Adrian M Wyard is a Seattle-based visual artist, and former designer & program manager at Microsoft. Currently focused on choreographed visuals for orchestra that include camera and audio reactivity.
Unfortunately I do have a new data point: Exporting in 2.3.0 has not fixed the problem. One minor addition: I noticed that after I try and Quit the unresponsive app the Force Quit dialog box never shows it as 'Not Responding' in Red - as usually happens with other failed Apps. But a Force Quit is needed to terminate it. (If I then start a new instance it works fine, as does the VDMX project which uses it.)
Other System info: MacBook Pro 15" (2015) with macOS 10.5 and the latest updates. Ableton Live 10 is also running on the system. Thanks!
Hi Jean Marie, I'm attaching two process sample files, one taken when the App was no longer working (but Task Manager didn't show it as unresponsive) and a second after I tried to Quit (and it has failed to do so). I'm also including the Vuo source and executable in case they are useful.
As 2.3.0 was just released I re-Exported the App and am now running that at the gallery. If we are lucky the problem will have gone away!
Hi Jean Marie, it's running as an exported app. I've learned a little more: the only symptom that something is wrong is the app stops working, and refuses to Quit. I didn't see anything noteworthy on the console until I Forced Quit when there were numerous mDNSResponder messages. I'm attaching those messages in case it's useful. The app has no network features (other than using OSC locally) but it does seem as though the problem has started since we enabled WiFi to support entirely unrelated network functionality. Does this info help at all?
●●●○ — It prevents me from completing a specific task with Vuo.
Steps causing the bug to occur:
I use a Vuo app as part of an installation and it hangs after a week or two requiring a full system restart. There doesn't seem to be any specific cause, so I'm guessing it's a memory-leak type of issue in Vuo or some related system component. But I'm not sure what I can do to help find the problem.
Have you found a workaround?:
No
Other notes:
The app is a Motion Monitor that reports motion across a video frame.
