AWS Thinkbox Discussion Forums

Beta 1 BUG Report

Deprecated Deadline 6 Bug Reports
#1

Hi,
OK, Here’s the list of what I could find a bit suspect in beta v1:

  1. OK, not related to beta v5, but since moving to Win7 OS as our main client OS, I’m getting a lot of invalid packet header size errors. Nothings changed with our Deadline 4.1 config, file servers remain the same, renderfarm size remains the same. Slave throttling is set to 30 start-ups at any 1 time. Same setting as before. Not sure why we might be getting more of this error than before. I guess I can only put this down to larger 3dsMax files being pushed around lately. ie: normal = 500-800Mb, recently its been 1.5GB. Max files submitted with the job and I know its at this point of the data transfer to the slave that this error occurs. I’m just wondering “if” Win7 OS is causing anything funky to happen? OK back to bug bashing…Here’s the actual error message I get for the job:

  1. Deadline monitor - right-click with NO job selected and click on “reports…” --> “View Log Report…”, etc causes 100% application crash.

  2. Keyboard shortcuts for viewing log reports, error, etc when again, no jobs in queue, causes monitor to crash.

  3. Deadline installer (client) drops a *.dll to root of C:\ drive during install but does not clean up after itself. Might be other files dropped elsewhere in the OS, but haven’t checked…

  4. Refreshing a job using the cache from Pulse and in the task list, the most recently “completed” frame shows correctly as completed BUT is always in “BOLD” font, which is different to the “normal” font display of a “completed” task. A second refresh resolves this graphics glitch and this most recent task is then displayed correctly. Doesn’t happen all the time…sometimes hard to replicate. One to watch for…

  5. Plugin Job Details are missing from the “tasks” menu in monitor

  6. Right-click; job properties dialog, needs to be wider. Getting cropped “rollout” box on the right-hand side in Win7 OS Aero Theme mode.

  7. Changing a custom “preLoad.py” to “preLoad.py.removeme” in a plugin directory causes a “hastable” error during rendering. Not good. Need to be able to temporarily disable a preLoad.py in a plugin folder. I guess I will have to just cut’n’paste the file out of the plugin directory to disable it?

That’s it for now :slight_smile:
Mike

#2

Thanks Mike!

  1. I’m not sure what would be the cause of this. The odd invalid packet error isn’t abnormal, but I have no idea why switching to Windows 7 would cause this to increase (or if it’s even the cause). Maybe it is the size of the max files. It’s one of those things you’ll have to watch for and see if a reduced load on the network or smaller max files results in a reduction in this error occurring.

If you had a copy of Vista or XP kicking around, maybe it’s worth the time to set up a slave or two that use one of these OS’s instead. If the problem happens less on these machines, then that could indicate it’s something with Windows 7.

  1. This menu item shouldn’t be available when no job is selected, so hiding it properly will fix this problem. This will be fixed in beta 3.

  2. See (2).

  3. I was able to reproduce this problem (msdia80.dll is the file that gets installed to the root folder). It turns out this is a known issue:
    support.microsoft.com/kb/927665

So we updated to the ATL Security Update version Microsoft recommends, and msdia80.dll was no longer installed to c:. This will be fixed in beta 3.

  1. I can’t seem to reproduce this one. I’ve seen the problem before in a previous version though, and we had addressed it back then. From looking at the code, I can’t see how this is even possible anymore. If you find a way to reproduce it reliably, let us know!

  2. We had removed this while testing out Remote Mode, and we found that not loading those properties made a major difference when loading individual jobs. We forgot to re-add it when not in Remote Mode. :blush: This will be fixed in beta 3.

  3. Confirmed. This will be fixed in beta 3.

  4. I can’t reproduce this one. I first created a PreLoad.py script and confirmed it was executed. Then I renamed it to PreLoad.py.removeme, and as expected, the script wasn’t executed. I tested with a simple plugin (Blender) and an advanced plugin (3dsmax) just to cover all bases, but the execution of PreLoad.py is the same in both cases, so as expected they both worked fine when the file was renamed. Would you be able to send us the log from the job with the error message so we can take a look?

Thanks!

  • Ryan
Privacy | Site terms | Cookie preferences