We see it use ram in the 2-5 gig range. Is that expected?

For the amount of data that’s in your Monitor, that’s not entirely surprising to see 2GB. 5GB seems excessive though. If you restart the Monitor, does it jump back up to 5GB, or is that something it grows to over time?

Fresh restart, it lingers around 80 megs for a while, then when the gui comes up shoots to 2 gigs for a bit, then down to 1 again (cpu going full tilt).

I start seeing the total job counter go up and up in 600 increments, and over a couple of minutes reaches our actual job count. Ram usage goes up to maybe around 1.1gigs.

At this point the monitor is not showing any jobs (status filters all turned off).

Turning on all filters to be shown, it takes about 30 seconds, and the jobs show up. Ram usage goes up to around 1.2 gigs, then starts fluctuating between 1.1 and 1.2, but overtime slowly creeping up. As i type this, its now over 1.2 gigs, and now dipping below (no user activity). CPU is mostly hovering around 100% usage on a single core.

Trying to delete ~10k jobs, selecting them is fairly quick, then right click menu takes about 15 seconds to come up. Being able to click Delete Jobs takes about 2-3 minutes (it does not highlight the option). After i click delete, ram usage starts going up steadily, reaching 1.8 gigs fairly quick (someone came by to ask me some question while i was testing this and before i could click “are you sure you want to delete=yes” so it could have been creeping up on its own to 1.8). Ill let it go, i imagine it will take a while…

after 6 minutes of the delete process running, its at 2.2 gigs of ram usage

Based on how long it took to delete 150 jobs earlier today, deleting these 10k might take a long time, so im not sure if i can monitor it all the way through…

yeah, we want to solve THAT particular problem as well…

Deletion has been going for 29 minutes now, ram usage is up to 4.1 gigs.

Weird though, if i open a monitor on another machine, it looks like the jobs have already been deleted

After ~35 mins, the monitor disappeared :\

Nothing in the monitor logs, event viewer entry:

Log Name: Application
Source: Application Error
Date: 11/6/2013 11:13:43 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: lapro3067.scanlinevfxla.local
Description:
Faulting application name: deadlinemonitor.exe, version: 6.1.0.53441, time stamp: 0x526fb5bb
Faulting module name: QtCore4.dll, version: 4.8.2.0, time stamp: 0x4fb35bf8
Exception code: 0xc0000005
Fault offset: 0x0000000000126de0
Faulting process id: 0x2258
Faulting application start time: 0x01cedb1cfb1d1eab
Faulting application path: C:\Program Files\Thinkbox\Deadline6\bin\deadlinemonitor.exe
Faulting module path: C:\Program Files\Thinkbox\Deadline6\bin\QtCore4.dll
Report Id: 8cb9be15-4717-11e3-af5d-0025909b7159
Event Xml:



1000
2
100
0x80000000000000

27559
Application
lapro3067.scanlinevfxla.local



deadlinemonitor.exe
6.1.0.53441
526fb5bb
QtCore4.dll
4.8.2.0
4fb35bf8
c0000005
0000000000126de0
2258
01cedb1cfb1d1eab
C:\Program Files\Thinkbox\Deadline6\bin\deadlinemonitor.exe
C:\Program Files\Thinkbox\Deadline6\bin\QtCore4.dll
8cb9be15-4717-11e3-af5d-0025909b7159

.NET event:

Log Name: Application
Source: .NET Runtime
Date: 11/6/2013 11:13:41 AM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: lapro3067.scanlinevfxla.local
Description:
Application: deadlinemonitor.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
at Python.Runtime.Runtime.PyObject_Call(IntPtr, IntPtr, IntPtr)
at Python.Runtime.Dispatcher.TrueDispatch(System.Collections.ArrayList)
at Python.Runtime.Dispatcher.Dispatch(System.Collections.ArrayList)
at FranticX.GenericDelegate0.Invoke()
at FranticX.GenericDelegate0.Invoke()
at Deadline.StorageDB.SettingsStorage.UpdateData(System.Object)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading._TimerCallback.PerformTimerCallback(System.Object)

Event Xml:



1026
2
0
0x80000000000000

27558
Application
lapro3067.scanlinevfxla.local



Application: deadlinemonitor.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
at Python.Runtime.Runtime.PyObject_Call(IntPtr, IntPtr, IntPtr)
at Python.Runtime.Dispatcher.TrueDispatch(System.Collections.ArrayList)
at Python.Runtime.Dispatcher.Dispatch(System.Collections.ArrayList)
at FranticX.GenericDelegate0.Invoke()
at FranticX.GenericDelegate0.Invoke()
at Deadline.StorageDB.SettingsStorage.UpdateData(System.Object)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading._TimerCallback.PerformTimerCallback(System.Object)

Looks like it was due to a memory issue (AccessViolationException). What we want to do is do all of this processing in a background thread so that the UI doesn’t lock up at all while the deletions are occurring. This is probably going to be one of our top priorities for 6.2.

Did the deletions finish properly i wonder…

If it goes into a background thread, what happens when you have a 40 min long deletion going on and you restart the monitor?

we’ll handle asynch cases. we’ve been doing work in stoke to that degree [simulation that can carry on after max closes etc]

cb