Announcement

Collapse
No announcement yet.

Double clicking previous render in the VFB history crashes Houdini

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Double clicking previous render in the VFB history crashes Houdini

    Hi

    Test scene here,
    https://drive.google.com/file/d/1j_U...ew?usp=sharing


    Steps to produce the crash
    -You will need to setup VFB history and do a quick test render to have something saved there, for example enable material override under options and set mode to lighting(just to have a quick fast render, as resolution is quite massive), now go to sampler tab and change noise threshold to .02 and do a production render
    -After render is finished, click the save icon in the VFB, Now you will need to clear the frame buffer using this icon

    Click image for larger version

Name:	Screenshot_118.jpg
Views:	307
Size:	28.4 KB
ID:	1047754

    -Now lets draw a render region and hit the play button

    Click image for larger version

Name:	Screenshot_119.jpg
Views:	271
Size:	14.2 KB
ID:	1047755

    -Now you will need to stop the IPR, and then from the history panel click the one render you saved before

    Click image for larger version

Name:	Screenshot_121.jpg
Views:	274
Size:	234.1 KB
ID:	1047756

    -Result, Houdini crashes without showing any messages
    I recorded a video here of the process,

    https://www.youtube.com/watch?v=kYHZ...ature=youtu.be

    Houdini 17.5.293
    Windows 10 1903
    Nvidia driver 436.15
    Latest Nightly

    best,
    Muhammed
    Muhammed Hamed
    V-Ray GPU product specialist


    chaos.com

  • #2
    HI Muhammed_Hamed , I can't reproduce this on my side. Is this happen with every scene or with a new history directory, with only few saved images? Or with smaller image resolutions?
    Georgy Chakarov | QA
    www.chaosgroup.com
    georgy.chakarov@chaosgroup.com

    Comment


    • #3
      it happens with every scene, and any saved renders
      Can I upload to you my render, so you put to your history directory?
      Maybe this can help your reproduce the issue

      And thanks for all your help, cheers!
      Muhammed Hamed
      V-Ray GPU product specialist


      chaos.com

      Comment


      • #4
        I think it's not needed, I'll just copy one big image a lot of times and will test it.
        Georgy Chakarov | QA
        www.chaosgroup.com
        georgy.chakarov@chaosgroup.com

        Comment


        • #5
          I really can't reproduce this crash even with more than a 100 4k images in the history directory.
          Georgy Chakarov | QA
          www.chaosgroup.com
          georgy.chakarov@chaosgroup.com

          Comment


          • #6
            I also could not reproduce this. Then I noticed your Task Manager in the video above - memory is 90+% full so I filled my PC's memory as well. Managed to get a crash following the same steps but before I log it, could you please verify the frame buffer is *not* crashing if you have some spare memory?

            Thanks!
            gosho.genchev@chaosgroup.com

            Comment


            • #7
              Hi Gosho.Genchev
              Yeah, it is definitely the case here.. I didn't realize I'm out of memory then, and I'm glad I recorded the video..
              I don't get that crash if I don't run out of memory on same machine(laptop), and I cannot reproduce on my main machine, that has 128 GB of RAM

              Thanks for your help!
              And thanks to Georgy as well

              Best,
              Muhammed
              Muhammed Hamed
              V-Ray GPU product specialist


              chaos.com

              Comment


              • #8
                Awesome, thank you for verifying that was the case.

                I'll log it, hopefully something can be done about the crash.

                All the best!
                gosho.genchev@chaosgroup.com

                Comment

                Working...
                X