When I select all my slaves in the monitor and right click to get the menu, then try to drill down into the remote control menu, my monitor freezes indefinitely every time. I’m using beta9 on windows. It seems that the monitor auto refreshing itself gets borked when too many slaves are selected.
-Nick
Hey Nick,
How many slaves are you selecting on average when this happens? Also, can you send us the Monitor’s log after it crashes?
Thanks,
Somewhere between 20 and 100 slaves is when it freezes. The monitor freezes indefinitely and then I have to kill it and restart it. All the monitor log shows each time is:
2013-01-15 10:22:28: BEGIN - DA059\n.burdan
2013-01-15 10:22:28: Deadline Monitor 6.0 [v6.0.0.49513 R]
2013-01-15 10:22:30: Main Window shown
This is actually beta8. Where there any changes made in this regard in beta9? I’ll install beta9 shortly and test with that.
Thanks for the info!
Definitely try updating to beta 9 to see if the problem persists. We did some work on the context menus between beta 8 and beta 9, so it’s possible the issue you’re seeing might have been fixed. Also, beta 9 fixes that slave memory leak you reported, so probably a good idea to update anyways. 
If the slave list still gives you problems in beta 9, let us know and we’ll log it as a bug.
Thanks!
I had upgrade everything to beta9 except my local monitor. Actually now that I upgraded the monitor to beta9, the freezing seems to have disappeared
Unfortunately I was wrong about this disappearing. Because of the auto-updating of the slave list, selecting more than, say 20 slaves, and then trying to access the right click menu is incredibly slow. Selecting more than 30 slaves and then trying to access the right click menu is impossible because the time it takes to update all the slaves table data is longer than the time between autoupdates so it seems to just get into an endless loop.
Thanks for confirming this is still a problem. We’ve logged it as a bug and will try to reproduce.
Cheers,