Search the Community
Showing results for tags 'v10'.
The search index is currently processing. Current results may not be complete.
hitting "stop" in the activities view with a grooming operation selected does not stop the selected operation. i have a runaway groom operation that is crashing retroengine. every time it crashes, it restarts itself and comes back trying to do the same groom. hitting the stop button seeming accomplishes nothing. the status of the task switches to "please wait...", then nothing happens for a while. then the engine eventually crashes again.
i'm seeing assertion failures from retrospect engine. oddly, they are happening at 5 minute intervals. they seem to be related to an instability i observed with client communications (reported under a separate thread). "Assertion failure at "grx.cpp-1089", on threadID <hexID>"
i'm running retro v10 console on my server, connected to the local retro engine and roughly every 5 mins, the console "blanks out", acting as though it has just restarted itself. it jumps up to the top level default display. from the log view within the retro console app, it appears that this is happening every 5 mins give or take a few seconds, with occasional "skips" where the interval is roughly 10 mins. in the console log view, i also see one odd msg of the form: "StucOpen: IOCreatePlugInInterfaceForService(kIOMMCDeviceUserClientTypeID) (error -536870210)". also, i had been away for a while and came back to the machine to find the console app had crashed. i have the crashdump and can post if it is useful. in this situation i'm running the latest retrospect v10 console and engine (installed ~4 days ago). the retro engine is running locally on the same box as the retro console. my system is running mac os x 10.6.8 server. in the system console on the machine, i see bunches of msgs at 5 minute intervals of the form "Server::updateScriptsCache exception: MacRequestor::Request: connection closed by remote endpoint" or " and other similar msgs involving updateSetsChangeCounter, updateSelectorsCache, etc. i'll post these log records as an attachment - it actually looks like there might be a lot of different things going on there that don't look familiar, including some scary-looking assertion failures - hmmm... RetroEngine or Retrospect.txt