Renderman 21.7 issue

Deadline
1

hi !

I freshly install the new version of rendman but Render with deadline not working , i try whith litle scene with juste a cube, but Rib generation work correctly but not render. I try to lunch render manualy in commande line and this work perfectly ! i dont understand because renderman 21.6 work perfectly

[code]=======================================================
Error

Error: Renderer returned non-zero error code, -1073741819, which represents a Memory Access Violation. There may not be enough memory, or the memory has become corrupt.
à Deadline.Plugins.PluginWrapper.RenderTasks(String taskId, Int32 startFrame, Int32 endFrame, String& outMessage, AbortLevel& abortLevel)

=======================================================
Type

RenderPluginException

=======================================================
Stack Trace

à Deadline.Plugins.SandboxedPlugin.d(DeadlineMessage aqi)
à Deadline.Plugins.SandboxedPlugin.RenderTask(String taskId, Int32 startFrame, Int32 endFrame)
à Deadline.Slaves.SlaveRenderThread.c(TaskLogWriter aha)

=======================================================
Log

2018-03-15 13:50:42: 0: Loading Job’s Plugin timeout is Disabled
2018-03-15 13:50:43: 0: Executing plugin command of type ‘Sync Files for Job’
2018-03-15 13:50:43: 0: All job files are already synchronized
2018-03-15 13:50:44: 0: Plugin RenderMan was already synchronized.
2018-03-15 13:50:44: 0: Done executing plugin command of type ‘Sync Files for Job’
2018-03-15 13:50:44: 0: Executing plugin command of type ‘Initialize Plugin’
2018-03-15 13:50:44: 0: INFO: Executing plugin script ‘C:\Users\Brice\AppData\Local\Thinkbox\Deadline10\slave\station09\plugins\5aaa690bd0bb123a5c11ab1d\RenderMan.py’
2018-03-15 13:50:44: 0: INFO: About: RIB Plugin for Deadline
2018-03-15 13:50:44: 0: INFO: Render Job As User disabled, running as current user ‘Brice’
2018-03-15 13:50:44: 0: INFO: The job’s environment will be merged with the current environment before rendering
2018-03-15 13:50:44: 0: Done executing plugin command of type ‘Initialize Plugin’
2018-03-15 13:50:45: 0: Start Job timeout is disabled.
2018-03-15 13:50:45: 0: Task timeout is disabled.
2018-03-15 13:50:45: 0: Loaded job: CRYPTOTEST2 (5aaa690bd0bb123a5c11ab1d)
2018-03-15 13:50:45: 0: Executing plugin command of type ‘Start Job’
2018-03-15 13:50:45: 0: INFO: Executing global asset transfer preload script ‘C:\Users\Brice\AppData\Local\Thinkbox\Deadline10\slave\station09\plugins\5aaa690bd0bb123a5c11ab1d\GlobalAssetTransferPreLoad.py’
2018-03-15 13:50:45: 0: INFO: Looking for AWS Portal File Transfer…
2018-03-15 13:50:45: 0: INFO: Looking for File Transfer controller in C:/Program Files/Thinkbox/S3BackedCache/bin/task.py…
2018-03-15 13:50:45: 0: INFO: Could not find AWS Portal File Transfer.
2018-03-15 13:50:45: 0: INFO: AWS Portal File Transfer is not installed on the system.
2018-03-15 13:50:45: 0: INFO: Executing global job preload script ‘C:\Users\Brice\AppData\Local\Thinkbox\Deadline10\slave\station09\plugins\5aaa690bd0bb123a5c11ab1d\GlobalJobPreLoad.py’
2018-03-15 13:50:45: 0: INFO: Looking for AWS Portal File Transfer…
2018-03-15 13:50:45: 0: INFO: Looking for File Transfer controller in C:/Program Files/Thinkbox/S3BackedCache/bin/task.py…
2018-03-15 13:50:45: 0: INFO: Could not find AWS Portal File Transfer.
2018-03-15 13:50:45: 0: INFO: AWS Portal File Transfer is not installed on the system.
2018-03-15 13:50:45: 0: Done executing plugin command of type ‘Start Job’
2018-03-15 13:50:45: 0: Plugin rendering frame(s): 2
2018-03-15 13:50:45: 0: Executing plugin command of type ‘Render Task’
2018-03-15 13:50:45: 0: INFO: Stdout Redirection Enabled: True
2018-03-15 13:50:45: 0: INFO: Stdout Handling Enabled: True
2018-03-15 13:50:45: 0: INFO: Popup Handling Enabled: False
2018-03-15 13:50:45: 0: INFO: Using Process Tree: True
2018-03-15 13:50:45: 0: INFO: Hiding DOS Window: True
2018-03-15 13:50:45: 0: INFO: Creating New Console: False
2018-03-15 13:50:45: 0: INFO: Running as user: Brice
2018-03-15 13:50:45: 0: INFO: Executable: “C:\Program Files\Pixar\RenderManProServer-21.7\bin\prman.exe”
2018-03-15 13:50:45: 0: INFO: Rendering file: M:\R_D\TEST\DEADLINE\renderman\CRYPTOTEST2\rib\0002\0002.rib
2018-03-15 13:50:45: 0: INFO: Argument: -Progress -t:0 “M:/R_D/TEST/DEADLINE/renderman/CRYPTOTEST2/rib/0002/0002.rib”
2018-03-15 13:50:45: 0: INFO: Full Command: “C:\Program Files\Pixar\RenderManProServer-21.7\bin\prman.exe” -Progress -t:0 “M:/R_D/TEST/DEADLINE/renderman/CRYPTOTEST2/rib/0002/0002.rib”
2018-03-15 13:50:45: 0: INFO: Startup Directory: “M:\R_D\TEST\DEADLINE”
2018-03-15 13:50:45: 0: INFO: Process Priority: BelowNormal
2018-03-15 13:50:45: 0: INFO: Process Affinity: default
2018-03-15 13:50:45: 0: INFO: Process is now running
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: *** exception ***
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: An application exception has occurred in prman.exe.
2018-03-15 13:50:46: 0: STDOUT: Error codes: 0x00007FFB5D64A2B6 0xC0000005 0x00000000 (0x00000000) (0x00000000)
2018-03-15 13:50:46: 0: STDOUT: Pixar PhotoRealistic RenderMan 21.7
2018-03-15 13:50:46: 0: STDOUT: copyright © 1988-2018 Pixar.
2018-03-15 13:50:46: 0: STDOUT: linked Mon Mar 12 22:32:09 2018 Pacific Daylight Time @1837774
2018-03-15 13:50:46: 0: STDOUT: build windows8_x86-64_vc11icc150_external_release
2018-03-15 13:50:46: 0: STDOUT: Rendered on Thu Mar 15 13:50:46 Paris, Madrid 2018
2018-03-15 13:50:46: 0: STDOUT: Rendering at 1920x1080 pixels, 512 maxsamples
2018-03-15 13:50:46: 0: STDOUT: “images/CRYPTOTEST2/CRYPTOTEST2.0002.exr” (mode = rgba, type = openexr)
2018-03-15 13:50:46: 0: STDOUT: Max resident mem: 972.65 MB
2018-03-15 13:50:46: 0: STDOUT: Page faults: 250192, Peak pagefile usage: 1935.64 MB, Peak paged pool usage: 0.30 MB
2018-03-15 13:50:46: 0: STDOUT: Real time: 00:00
2018-03-15 13:50:46: 0: STDOUT: User time: 00:00
2018-03-15 13:50:46: 0: STDOUT: Sys time: 00:06
2018-03-15 13:50:46: 0: INFO: Process exit code: -1073741819
2018-03-15 13:50:46: 0: Done executing plugin command of type ‘Render Task’

=======================================================
Details

Date: 03/15/2018 13:50:48
Frames: 2
Elapsed Time: 00:00:00:14
Job Submit Date: 03/15/2018 13:37:31
Job User: brice
Average RAM Usage: 28191088640 (42%)
Peak RAM Usage: 28191088640 (42%)
Average CPU Usage: 9%
Peak CPU Usage: 59%
Used CPU Clocks (x10^6 cycles): 19108
Total CPU Clocks (x10^6 cycles): 212309

=======================================================
Slave Information

Slave Name: STATION09
Version: v10.0.11.1 Release (b0f2000be)
Operating System: Windows 10 Professionnel
Running As Service: No
Machine User: Brice
IP Address: 2620:9b::191c:7cfb
MAC Address: 7A:79:19:1C:7C:FB
CPU Architecture: x64
CPUs: 40
CPU Usage: 2%
Memory Usage: 26.3 GB / 63.9 GB (41%)
Free Disk Space: 1.184 TB (66.235 GB on C:, 1.120 TB on D:)
Video Card: NVIDIA GeForce GTX 980 Ti[/code]

2

Hmm. An Access Violation is the usually bad memory management bug. You have more than enough free RAM so it’s not a memory pressure problem.

You’re also not running Deadline as a service so it should be a 1:1 test…

Did you run Renderman on “STATION09” when you were testing? There were 40 access violation exception so it looks like every sub-process (or thread) that was started per core died…

3

I tried in service mode and not in service mod , i have this bug on all machine and i try to lunch renderman in commande line on my machine “STATION09” and on FARM machine with no another proces runing in same time

4

Looks like a known issue on the renderman forum, I have the same issue

renderman.pixar.com/forum/showt … adid=36438

5

Hahahah this is my post ^^ and this issue it’s only in specific case i’ts a bug in Renderman engine and this produce with deadline AND in commande line :slight_smile:

6

So it’s not working either way? I need to dig up my Pixar login credentials and follow along.

7

To make sure we understand each other well. The post on the Pixar forum is referring to another bug that I had before. It has nothing to do with the current bug. It is a problem with too much light intensity on windows.

My renderman 21.6 works very well (out of the bug with too much light intensity) on the command line and on deadline. But Renderman 21.7 works well on the command line but not with deadline, it’s only with deadline that renderman 21.7 does not work

I try to run the command line as it is in deadline on my machine in manual, and it works very well, it is only when it is deadline that execute this command that it does not work

8

After a lot of testing I managed to render some images with renderman 21.7 on deadline. Maybe the problem comes from renderman I’m going to discuss with them on the forum

But it’s still strange I’m this error only with dealine, no error in command line

9

It looks like they’re aware of something, reading your thread on the pixar forum (i googled the error and ended there). The last post said they were working on a fix

strangely I had the issue in both deadline and commandline

I had to reboot this morning and the problem isn’t there (at the moment!) render fine on commandline and deadline. It be a required reboot thing or is it just random?

10

I already try to restart all my farm has nothing to change, in doubt I will retry

Edit: I reboot all of my farm with a minor windows update and a this moment no bug anymore :open_mouth: strange, i continue my test but a this moment this problem was solved with windows update how knew !