Auto reopen on crash

Skulpture

The patch is doing quite basic stuff;

- Pick 1 of 6 videos and plays it.

- If no video is chosen after 2 mins it plays a demo video.

But it will be running all day 5 days a week. It keeps hanging up after *about* two hours.

I am sure I will sort it out but I can't seem to understand why its happening right now.

particlep

i sounds quite a quandary. could it be at all related to a system thing like put hard disc to sleep after 2 hours? r u testing the patch by letting the demo run every two minutes ? does this all take place in the same scene ? my approach here is asking questions with the intention of doing things with the stuff u already know.

Skulpture

Nope all energy saving and screen savers stuff is off; checked that.

Demo video is running every 2 mins with me now and again triggering a video.

Videos are in various scenes, so no not just one.

Weird huh?

particlep

oh yes ! do you suspect it to be connected to quicktime memory leakage filling up the ram ?

nick

have you looked at the console output ot see of there are any clues in there ?

Skulpture

@particlep - I have a feeling that's it.

@nick yes but it doesn't mean much to me. My coding/programming skills are next to nothing...

particlep

i"m only aware of it as i"m remembering a post somewhere on the original forum by mark about it. as a way of testing it, if u were to make a demo video file that is twice the size of the existing demo file, what do u see happen to the mean time to hang ?

Skulpture

In fact it just did it now.... lasted about 3hrs25mins (approx).

Again no crash, just pauses and then beach ball.

I have saved the crash file console output (wont let me attach it here as a ZIP for some reason)

Skulpture

Attached it.... 01d33d-izzy-crash-gt.rtf

particlep

can you run the patch on an older mac with an older operating system at all to check if it's something connected to mac os?

Skulpture

I can try that yes. I might give it a go tomorrow.

particlep

i found this

http://lists.apple.com/archives/quartzcomposer-dev/2012/Mar/msg00000.html

in it there''s a reference to the opngl driver monitor. i have no idea what it is, but it seems to monitor something, that might be useful. i might just have to make a cup of tea, as i don;t think i'm adding too much now.

Skulpture

Thanks for your thoughts though @particlep I appriciate it :-)

On a brighter note - my work macbook pro retina just arrived! Woo!

vanakaru

Try to ask help from these guys

http://hintsforums.macworld.com

There are some great enthusiasts who also are good reading clues from the console logs.

It may have something to do how many times a loop is allowed to play by the system(or Isadora?). Original size 2 hours 2x the size almost 4 hours?!

Skulpture

Thanks will do @vanakaru

Skulpture

I have created a post on the macworld forum; but waiting validation, etc.

I have also seen that it's happening on similar software such as max/msp+jitter:

http://cycling74.com/forums/topic.php?id=28251

And processing:

http://processing.org/discourse/alpha/board_Proce55ing_software_bugs_action_display_num_1106328253.html

This is a huge issue, can't understand how or why Apple have done this?

nick

Its an assumption at the moment that those other issues are the same as yours - one is from 7 years ago, so may not be a live issue any more.

Can you post your patch - there might be something unusual in it that you may not have noticed ?

Try running your patch with Activity Monitor running (found in the Utilities folder) to monitor its memory use as it runs - it may provide a clue.

mark

Dear Graham,

OK -- I've looked over the crash report. It seems like there are dozens of movies that are attempting to be loaded in the background. For sure this shouldn't happen, but it could be a result of your randomization routine. What I think might be happening goes like this:

1) Movie 1 is playing

2) You request movie 5 (i.e., send a 5 to the 'movie' input)

3) Background preload of movie 5 starts; movie 1 continues to play

4) Before the background preload of movie 5 completes, you request a different clip -- e.g., movie 6 -- by sending a 6 into the 'movie' input

5) Movie 5 goes off to the nether world, consuming memory and resources

6) Movie 6 plays, movie 1 gets properly "thrown away"

Repeat this process enough, and eventually, you run out of memory.

Is this possible Graham? That the random numbers are coming so rapidly, that the a new movie would be chosen before the old one is preloaded?

One simple test: put a Multi Blocker before the 'movie' input -- set the value to 2 seconds. (I know that may be too long... but just as a test.) If you do this, does the patch run without crashing for a substantially longer time?

Also, you should really try this patch with 1.3.0f26 if you haven't already. I may have addressed some bugs in this area that will get it to run better. But try the test above first if at all possible, so we can zero in on the problem.

Best Wishes,

Mark

Skulpture

Hi Mark,

First off all thanks for looking into this, and thanks to everyone else above for chiming in and helping.

The routine you described is not how I've patched i'm afraid; but it still helps me out and has given me an idea of how to improve the patch drastically.

Each movie player has its own projector and when video one is picked; its turns on movie player 1, when video two is picked it turn on video two. I have used to toggle on/off for visibility on each of the movie players but am starting to think this is not the best way to go about it.

After each video isadora jumps to a secondly scene (jump connected to video end) this plays another video and then goes back to the first scene awaiting a new video to be picked.

I will try and attach a screen shot today. I am going to explore this all day today.

I did also update to 1.3.0f26 yesterday and did see a bit of a difference yes.

Again; thanks to everyone.

Skulpture

I think i've solved the problems.... re-designed the patch.