Next Update 3: Crash after canceling or finishing a render

Hey guys,
after Update 3 we get a lot of instant crashes after canceling or finishing a render. As soon as you hit Esc key, Max crashes. Anyone with similar experiences?

Have a similar problem since some weeks, may be that is in relation to yours. When I hit the render button while interactive rendering is active in the VFB window MAX hangs, but I can save the changes. I´m not able to close the VFB or the render progress window, but I´m able to close for example the material browser or I can save and quit MAX. Is your interactive rendering active when you start to render?

No. This is production rendering in bucket mode. We have this issue on 3 identical workstations in different scenes.

My problem was also with production renderimg. But I didnt stop interactive rendering before I hitted the render button for production rendering. When I stop interactive renderung in the VFB before that all works fine.

I can definately say that the IPR was stopped before starting production render.

I created two dump files after a crash. Where should I send them to?

You can attach them here or send them to support (support at chaosgroup.com).

Okay, here they are. I hope a solution can be found because right now Update 3 is too unstable to use in production.
3dsMax_Minidumps.zip (3.64 MB)

Thanks for the dumps - not much info so far - it seems something crashes inside the Max bitmap manager. Could you try to convert any bitmaps to VRayHDRI and see if anything changes while we are investigating.

This could make sense, because sometimes we get a crash while browsing out material library. While the swatches calculate the preview image, we get the crash.

I can not confirm that converting to VrayHDRI is a solution to that problem.

Crash dump after conversion to VrayHDRI.
3dsmax_minidump03.zip (1.85 MB)

Thanks for the heads-up here guys. I have a Monday deadline that this could have quite dramatically screwed with if I hadn’t had chance to test it,
which I will do tomorrow and see if it is replicable.

The new dump still seems to be somewhere in the Max bitmap manager - something related to the view port background image.
We are also still trying to find what causes it.

I checked the viewport background files, nothing extraordinary. It is an 8bit Jpeg, RGB Color. We had issues with CMYK files in the past, but it is none of these issues.

Ok, so far I’ve found a temporary workaround - open the scene, switch to scanline (this will loose the settings so save some preset maybe) and save the scene. Then close Max, open it again and open the scene with scanline. Then switch back to V-Ray and save - the scene should work correctly now.

The actual issue is somewhere in the VFB settings V-Ray saved in the scene - when we load them something goes wrong and somehow messes up the Max Bitmap Manager. Those messed up settings only happen in some V-Ray versions - the newest version should save the settings correctly.

I now have to find what setting is actually messed up and how to read it correctly.

Actually I was wrong it might not be related to the saved settings. Do you use the test resolution toggle in the VFB? If so - do you get crashes if you don’t use it at all for the whole Max session ?

I did not use the test resolution settings at all after we upgraded to Update 3. In all the sessions I had, I did not use it and still experienced crashes. These were random though, sometimes the render finished or canceled without issues.

However, I can not guarantee that one of my colleagues used test settings button before I took over, so maybe something got messed up the first time it was used?

In the meantime, disabling the viewport background image seems to help, but this can only be seen as a temporary fix. We will have to use the viewport background in the not so distant future…

Alright, so here is another minidump and logfiles for another crash that happened today. Not after finishing or canceling a render, but simply by opening the material editor. This is getting worse!
3dsmax_minidump04.zip (2.07 MB)

Could you try the latest stable nightly (29754) - we’ve added a fix that we hope will help.