Auto reopen on crash
-
I have turned Marks script into an App. Just for those who find it easier to work with; I use it this way so on start up the machine automatically loads this app and kick stats isadora.5a886c-isadora-watcher-mc.app.zip
-
I now have a new problem..... After about two hours of running an Isadora patch it is locking up. No crash. Just goes still and as soon as I move the mouse I get the spinning beach ball.
This patch needs to run for 8 hours a day; best I can get is 2 hours. Bit worried. Does anyone know if I can make automator look for "not responding" instead of crash... because Isadora isn't even crashing.I have a feeling this is a Quicktime issue.... -
i wish i could help skulpture but i feel all i can do is offer supportive words in a post following yours. can i ask what the patch is doing, sorry i mean what does isadora output and is the 2 hour thing in any way related to a mulitiple of the loop time of the piece, i have of course gone for the big assumption of a looping video....
-
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. -
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.
-
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? -
oh yes ! do you suspect it to be connected to quicktime memory leakage filling up the ram ?
-
have you looked at the console output ot see of there are any clues in there ?
-
@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... -
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 ?
-
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) -
Attached it.... 01d33d-izzy-crash-gt.rtf
-
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?
-
I can try that yes. I might give it a go tomorrow.
-
i found this
http://lists.apple.com/archives/quartzcomposer-dev/2012/Mar/msg00000.htmlin 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. -
Thanks for your thoughts though @particlep I appriciate it :-)
On a brighter note - my work macbook pro retina just arrived! Woo! -
Try to ask help from these guys
http://hintsforums.macworld.comThere 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?! -
Thanks will do @vanakaru
-
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=28251And processing:http://processing.org/discourse/alpha/board_Proce55ing_software_bugs_action_display_num_1106328253.htmlThis is a huge issue, can't understand how or why Apple have done this? -
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.
