Announcement

Collapse
No announcement yet.

(Resolved) VRay Houdini Standalone Crash after completed frame is written.

Collapse
This topic has been answered.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • (Resolved) VRay Houdini Standalone Crash after completed frame is written.

    We are still being plaugued by a crash after the finished frame is written to disk.

    The attached job is the worst one I have seen with just about every frame doing it.

    I have included the log - nothing seems to be going wrong - it just segfaults and quits.

    Most jobs only do it on one or two random frames, but some do it on a lot more. We haven't identified any correlation between the crashes and the type of scene.

    Everything is running Rocky9
    Houdini 20.5, Vray 62020
    Attached Files
    Last edited by Dubbie99; 09-02-2025, 10:51 PM.
  • Answer selected by Gosho.Genchev at 17-02-2025, 03:42 AM.

    Hello again, I've just spoke with the devs. There are two env vars which might help - VRAY_TERMINATE_ON_FRAME_END and VRAY_TERMINATE_ON_SEQUENCE_END​. Can you try them and see if they help?
    https://docs.chaos.com/display/VNS/V...ment+Variables
    Last edited by chakarov; 10-02-2025, 03:19 AM.

    Comment


    • #2
      One extra piece of info - it still happens even if write files is turned off. So it's nothing to do with writing the exrs.

      Comment


      • #3
        Hello Dubbie99 , I'll take a look and will write back to you when I have more info.
        Georgy Chakarov | QA
        www.chaosgroup.com
        georgy.chakarov@chaosgroup.com

        Comment


        • #4
          Hello again, I've just spoke with the devs. There are two env vars which might help - VRAY_TERMINATE_ON_FRAME_END and VRAY_TERMINATE_ON_SEQUENCE_END​. Can you try them and see if they help?
          https://docs.chaos.com/display/VNS/V...ment+Variables
          Last edited by chakarov; 10-02-2025, 03:19 AM.
          Georgy Chakarov | QA
          www.chaosgroup.com
          georgy.chakarov@chaosgroup.com

          Comment


          • #5
            Thanks for the suggestion.
            We tried this and are still getting the segfault immediately after:

            Code:
            [2025/Feb/11|10:20:20] [11714 MB] Maximum memory usage for attributes: 0.00 MB
            [EDIT]

            Looks like I spoke too soon - the Environment variable was not being passed properly to the render environment. After fixing this, it seems like it solves the problem.
            Thank you for the solution!
            Last edited by Dubbie99; 10-02-2025, 04:41 PM.

            Comment

            Working...
            X