I cannot comment on the specific error code, other than it looks similar to most errors I got when a job crashed ( even when a crash was not directly related to the render engine). Does it also crash, when rendered locally via xsibatch on the workstation? That would at least out rule the farm and RR...
Which renderer ar you using btw? Are there any debug modes like mental ray has? Maybe this will give a hint too. Sven -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Morten Bartholdy Sent: Friday, March 03, 2017 3:51 PM To: Official Softimage Users Mailing List. https://groups.google.com/forum/#!forum/xsi_list Subject: Re: Scene crashing on the farm - renders in the UI I am troubleshooting a scene which repeatedely crashes when rendering on the farm (RR) or using xsibatch, but renders fine in the UI Renderregion. I get these error messages: ---------------------------------------------------------------------------- ----------------------------- R160| >"C:\Program Files (x86)\rrService\lc64\rrCheckexitcode.exe" -1073741819 0 0 6 R161| ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++ R162| +++++++++++++++++++++++++++03.03. 15:41.43 Render Executable done +++++++++++++++++++++++++++++++++++ R163| ++++++++++++++++++++ Royal Render checks the return code of the executable ++++++++++++++++++++ R164| ++++ Executable returned -1073741819 (0x c0000005) as exit code for frame 6. R165| Error: Renderer or plugin contains a bug. Crash was caused by a NULL pointer memory access. R166| ++++ Executable crashed C 0| ************************* CLIENT REPORTS DURING THIS RENDER ************************* C 3| Error in this log file (240): error: renderer or plugin contains a bug. crash was caused by a null pointer memory access. C 4| C 5| Job crashed ---------------------------------------------------------------------------- ----------------------------- I suspected a hickup with a large referenced model and deltas, so I deleted this and reimported and partitioned elements in it again, but the scene still crashes. Does anyone here know what these errors mean and what might cause them so I know what to look for for a fix? Thanks Morten > Den 2. marts 2017 klokken 10:22 skrev Orlando Esponda <[email protected]>: > > > Try to get rid of the Redshift options. It's been a while since I used > Royal Render but I remember it stops the render if it finds any kind of > error in the scene. Deleting renderer options is not that easy to do > manually, I recommend doing it via script. > > try this: > > from win32com.client import constants as c > > si = Application > log = si.LogMessage > > RENDERER_NAME = "Redshift Options" > > renderOptionsList = [] > > for cstmProp in si.FindObjects("", > "{76332571-D242-11d0-B69C-00AA003B3EA6}"): > if RENDERER_NAME in cstmProp.Name: > log(cstmProp.FullName) > renderOptionsList. append(cstmProp) > > for renderer in renderOptionsList: > si.DeleteObj(renderer) > > > > > On Thu, Mar 2, 2017 at 2:54 AM, Morten Bartholdy <[email protected]> > wrote: > > > Hi all, > > > > I have a scene which has rendered fine until now, but after some modeling > > and shader changes in a referenced model (performed on the master and > > referenced in) it crashes on the farm (RoyalRender) but renders fine in the > > UI RenderRegion. > > > > I made some shader and scale changes to assets in a referenced model after > > which this occurs, but I am not sure how that could be the problem. I am > > not sure what to make of the bug info - any ideas? > > > > I actually see a number of messages pertaining to a large number of deltas > > not being applied to objects in a referenced model, like this: > > > > R144| ' WARNING : 3000 - Cannot apply Delta Road, because the target model > > Landscape_01.Delta2 is invalid. > > > > After these messages I see this: > > > > R318| * CRASHED in C3DStaticCompArray::Set at 00:00:00 > > R319| * signal caught: error C0000005 -- access violation > > > > - later again: > > > > R417| >"C:\Program Files (x86)\rrService\lc64\rrCheckexitcode.exe" > > -1073741819 0 0 12 > > R418| ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > +++++++++++++++++++++++++++++++++++ > > R419| +++++++++++++++++++++++++++03.01. 17:51.01 Render Executable done > > +++++++++++++++++++++++++++++++++++ > > R420| ++++++++++++++++++++ Royal Render checks the return code of the > > executable ++++++++++++++++++++ > > R421| ++++ Executable returned -1073741819 (0x c0000005) as exit code for > > frame 12. > > R422| Error: Renderer or plugin contains a bug. Crash was caused by a NULL > > pointer memory access. > > R423| ++++ Executable crashed > > > > - and: > > > > C 0| ************************* CLIENT REPORTS DURING THIS RENDER > > ************************* > > C 1| > > C 2| Error in this log file (213): ' error : 2356 - this plug-in is not > > installed: redshift options > > C 3| Error in this log file (394): * signal caught: error c0000005 -- > > access violation > > C 4| Error in this log file (497): error: renderer or plugin contains a > > bug. crash was caused by a null pointer memory access. > > C 5| > > C 6| Job crashed > > C 7| > > C 8| > > > > > > It doesn't ring any bells with me except for the delta/ref model messages, > > and the only way I know to fix that is delete the offending refmodel and > > reload it in the scene, which I would prefer to avoid. > > > > Given that the crashing is caused by the delta trouble, does someone here > > have any ideas regarding how to clean/fix the refmodel delta's or is the > > only way to delete and load it again and redo all partitioning? > > > > > > Thanks > > Morten > > ------ > > Softimage Mailing List. > > To unsubscribe, send a mail to [email protected] > > with "unsubscribe" in the subject, and reply to confirm. > > > ------ > Softimage Mailing List. > To unsubscribe, send a mail to [email protected] with "unsubscribe" in the subject, and reply to confirm. ------ Softimage Mailing List. To unsubscribe, send a mail to [email protected] with "unsubscribe" in the subject, and reply to confirm. ------ Softimage Mailing List. To unsubscribe, send a mail to [email protected] with "unsubscribe" in the subject, and reply to confirm.
