Itoo Software Forum

Author Topic: (Trapped SEH Exception in CurRenderRenderFrame(): Access vilation  (Read 299 times)

iToo_Butler

  • Jr. Member
  • **
  • Posts: 56
    • DJS CGI
Hi all,

I'm having some rendering issues on two machines. They are new. Windows 10. Forest pack 6.1.5. (I know there are newer versions but i'm currently keeping the file and all plugins as they are on the network to minimise any potential issues.

When I open the problematic file locally and render a frame, both machines render with no issues. But when I send them to our render farm which is running Deadline, they crash. The error log halts when it reaches a certain Forest Pack object (which seems to be different each time) and throws the following message for instance 'Forest_low_grass_connection' : Starting BuildMesh(11520)

I have sent the error log to Thinkbox support but they haven't managed to help me with any answers yet. I've posted here purely because it seems to error on a Forest pack object.

If anyone has any ideas as to what might cause these Unexpected exception (Trapped SEH Exception in CurRenderRenderFrame(): Access violation error I'm all ears for a solution!

Best regards

Andy.
Cheers,

iToo_Butler.

iToo

  • Administrator
  • Hero Member
  • *****
  • Posts: 3555
    • iToo Software
Re: (Trapped SEH Exception in CurRenderRenderFrame(): Access vilation
« Reply #1 on: May 31, 2019, 08:16:02 AM »
Hi Andy,

Unfortunately without the minidump we cannot identify the problem, because the error is too generic (just an exception was triggered).
This is the documentation from Deadline:

Trapped SEH Exception in CurRendererRenderFrame(): Access Violation

An Access Violation means that when rendering the frame, Max either ran out of memory, or memory became corrupted. The stack trace in the error message usually shows which plugin the error occurred in. If that doesn’t help track down the issue, try stripping down the max file by deleting objects and seeing if the error still occurs.

If the last line of your job log report showed INFO: Lightning: Overriding save file option to 0 as the message, it may be related to one or more of your render output paths, including Render Element file paths being > 255 characters in length (Windows OS limitation). To resolve, simply reduce the overall length of the file path you are saving your renders to. Bear in mind, if using V-Ray’s VFB “Separate render channels” option, the overall file path may be longer than you can currently visualize inside of 3ds Max prior to network render submission. If enabled, there are SMTD Sanity Check’s to test for this situation during submission.


What render engine do you use ?

I would suggest to try a render using Backburner, to see if there is any difference, or at least Max generates the minidump and we can get more information.

Regards,

Carlos Quintero
iToo Software

iToo_Butler

  • Jr. Member
  • **
  • Posts: 56
    • DJS CGI
Re: (Trapped SEH Exception in CurRenderRenderFrame(): Access vilation
« Reply #2 on: May 31, 2019, 09:19:49 AM »
Thanks for that.

I've searched that relevant machines for the mini dump but none of them have one. Perhaps because they are network rendering machines and 3dsmax didn't error correctly to create one? I cna send the deadline log if that helps?

It does note Forestpack.dlo as the module that errored.

Currently rendering with VRay next.
Cheers,

iToo_Butler.

iToo

  • Administrator
  • Hero Member
  • *****
  • Posts: 3555
    • iToo Software
Re: (Trapped SEH Exception in CurRenderRenderFrame(): Access vilation
« Reply #3 on: May 31, 2019, 09:47:29 AM »
Checking our release notes, i see a couple of fixes that would be related with this case:

Forest Pack 6.1.6
- Fixed crashing bug with Animation modes in V-Ray.

Forest Pack 6.1.6
- Fixed critical bug in multithreaded scattering processes.

So i encourage you to upgrade to the latest FP release (6.2.1).

Carlos Quintero
iToo Software