Deadline 8 Monitor Crashing

Hi,

I’m seeing some fairly consistent crashing in the Deadline 8 Monitor (Windows 7) when navigating the panels. I can pretty much guarantee a crash by clicking between different jobs, after less than 10 clicks the monitor greys out. we’re not particularly busy at the moment with only about 75 jobs on. Any thoughts?

Thanks

Nick

Hey,

How odd. I was testing Monitor with 20,000 jobs only last week and it was performing well! Can you zip up your monitor logs and send them over?

docs.thinkboxsoftware.com/produc … ation-logs
docs.thinkboxsoftware.com/produc … ml#monitor

Just to be super-sure, if you open a Command Prompt, change directory to: “C:\Program Files\Thinkbox\Deadline8\bin” and execute: “deadlinemonitor.exe”. Play with Monitor to try and make it crash, then if it does, the error/stack trace should be captured in the command prompt. right-click in Command Prompt -> “mark”, drag and select applicable text and hit “enter”, then copy’n’paste the text to here!

Hi Mike,

I’ve done as you suggested and it crashed in the same way but I get no details on the crash in the Command Prompt. There also seems to be no details in the Monitor logs going back through them. All I see is what is below:

Nick

Hmmm…odd. I’ve got just over 10,000 jobs in my local queue and I’ve made about ~100 odd mouse clicks between different jobs so far, and no problems at all. I think our support team will need to take a closer look at your setup. Can you create a support ticket and they can arrange a time to remote in? support.thinkboxsoftware.com

Thanks Mike, I’ll do that now.

Hi there,

I think to get a stack trace in a command shell, you need to run deadline in “console mode”.

For that, one parameter was missing from Mike’s suggestion:

Change directory to: “C:\Program Files\Thinkbox\Deadline8\bin”
execute: “deadlinemonitor.exe -console

Then you should get the trace on crash

OK, that got it. Error report below:

It spewed out the Missing .NET errors but still carried on working as I clicked through the jobs then shortly after crashed completely.

Important crash info from our call today:

The access violation exists within NativeThinkboxUIC++.dll. I’ve been unable to reproduce on our side yet, but I noticed a slight slugishness in the Monitor UI on Weedy’s side that I’ve only seen on one machine over here. I’ll have the man who owns the machine test things out there.