Hi Ryan,
I just had Pulse crash on me when I came in this morning. Pulse has been running since Monday or Tuesday on that machine. Well, since I downgraded to Mono 2.6.7. really. Anyway, when I came in this morning, the machine asked for my admin password claiming that the Developer Tools Access need elevated permissions. After I gave my credentials, Pulse crashed. Slave and Launcher kept running undisturbed though.
Also I haven’t yet upgraded to RC1. Was going to do that today.
Here is the crash log.
mono_2011-11-25-093830_chef.txt (49.3 KB)
Very weird! Have you been prompted for Developer Tools elevation since? Has Pulse crashed since? I’m just wondering if this was some random one-off issue, or if it’s repeatable.
Cheers,
First and last time it happened so far. I’ll keep an eye open and if it ever happens again I’ll shout.
It happened again just now only this time it was the slave that crashed after I gave my admin credentials. Still not running RC1. Haven’t got time to upgrade yet.
Both times it happened on the machine running 10.7.2
mono_2011-11-29-143906_chef.txt (53.5 KB)
The crash appears to be occurring in X11, so theoretically if you ran the slave and pulse in “nogui” mode, it shouldn’t cause them to crash. You can start the slave or pulse in nogui mode from a terminal:
deadlineslave -nogui
deadlinepulse -nogui
Of course, that’s not a proper solution, but it might work in the meantime if this becomes a common problem for you. The next time you are prompted, would it be possible to take a screen shot? It would be nice to try and figure out why you are being prompted like this, and if there is any way to prevent it.
Cheers,
Hi Ryan,
I have been running the Slave and Pulse in nogui mode with great success. However, Pulse still keeps crashing once in a while. I have attached the crash output from the Terminal window.
PulseCrash.log (86.3 KB)
and just got another, different, one:
[code]ERROR:…/…/mono/io-layer/handles-private.h:362:_wapi_handle_share_release: assertion failed: (info->handle_refs > 0)
Stacktrace:
at (wrapper managed-to-native) System.IO.MonoIO.Close (intptr,System.IO.MonoIOError&) <0x00004>
at (wrapper managed-to-native) System.IO.MonoIO.Close (intptr,System.IO.MonoIOError&) <0x00004>
at System.IO.FileStream.Dispose (bool) <0x00094>
at System.IO.Stream.Close () <0x0001b>
at System.IO.StreamReader.Dispose (bool) <0x0002a>
at System.IO.StreamReader.Close () <0x00018>
**
ERROR:…/…/mono/io-layer/handles-private.h:362:_wapi_handle_share_release: assertion failed: (info->handle_refs > 0)
Abort trap: 6[/code]
I wonder if it’s a threading issue…
In the Pulse Settings in your Repository Options, under the General tab, try setting Dedicated Data Loading Threads to 1, and then restart Pulse. Let it run for a few days to see if the problem creeps up again. If it doesn’t, then it’s probably safe to assume there is a threading issue here.
Had Pulse running with Dedicated Data Loading Threads set to 1, but it still crashes. I have attached the current Terminal dump.
PulseCrash.log (84.2 KB)
I googled the error, and found this:
lists.ximian.com/pipermail/mono- … 94073.html
There is a command there that apparently helps on Linux, but ipcs is available on OSX too. Before doing that though, have you tried rebooting the Pulse machine, or uninstalling/reinstalling Mono on it? If not, it’s probably worth trying that first. For uninstalling Mono, you can use this script:
mono-project.com/Mono:OSX#Un … n_Mac_OS_X
Will give it a try. Might take a while though since all machines are rendering for a project. Don’t really see a timeslot for rebooting till mid-next week. But we are doing fine without Pulse.