Crash when rendering animation in Workbench (with workbench shadows)
Confirmed, NormalPublic
Actions

Description

System Information
Operating system: Windows 10 20H2
Graphics card: Nvidia GTX1080

Blender Version
Broken: 2.93.0
Worked: 2.92.0

Short description of error
When rendering the attached file as animation Blender ends without notice after the second rendered frame.

mirandaAnimNeu3.blend1 GBDownload

Exact steps for others to reproduce the error
Open the file mirandaAnimNeu3.blend. Click Render | Render Animation.

The animation is set to start at Frame 466 and to last until frame 4900. After rendering of frame 467 Blender crashes without notice. No crash file is created. Blender just ends.

Both rendered images are saved. It is interesting to note that the earlier images of this animation are rendered within seconds but the render times of the last images require minutes although no noticeable content becomes visible. Yesterday I have rendered all 4900 frames at 50% size without anti-aliasing, which worked fine. Each image rendered in a second or two.
Sorry that the blend-file is so big...

Related Objects

Mentioned Here: T78161: Workbench refactor causes significant performance regression with workbench shadows
M1: Bevel Tool Toolbar Layout - Multiple Overflow Popovers

Event Timeline

Hans Classen (hc3d) created this task.Jun 7 2021, 9:49 PM

I cannot get that large Blend file to download. Maybe you had better placed it on OneDrive or Dropbox.

@Leon Zandman (lzandman) All files necessary to reproduce issue should be uploaded to this site directly.

@Hans Classen (hc3d) We require as simple as possible files to demonstrate the issue. Can you simplify your file by removing as much elements as possible that don't contribute to crash?

In T88933#1172850, @Richard Antalik (ISS) wrote:

@Leon Zandman (lzandman) All files necessary to reproduce issue should be uploaded to this site directly.

OK. The download did start after a while. I tried rendering the first frame on my MacBook M1, but it completely froze Blender. Could be that my laptop just isn’t beefy enough for this heavy file. Though that still shouldn’t cause a full freeze.

This is an alternate download link from my HiDrive:
https://my.hidrive.com/lnk/u0YESfcM

After loading, Blender reports 4.14GB Memory and 1.1 GB video memory. Loading takes a while actually. Therefore I have the file on my SSD.

This is the structure of the complete scene:

The crash happens as well when I deactivate the first three (comparably small collections):

When I delete the three collections, save the file, end Blender, restart Blender and load the file without the three collections, the crash happens again.
No Blender_crash.txt file is created.
When I delete the collection called "Miranda" from the complete file, rendering works fine.
I have not uploaded a new file as the file is only some kB smaller without the three collections. Blender reports 3.9GB memory compared to 4.1GB with complete contents.
In result, it appears that the crash depends on the collection "Miranda", which is made up of quite a hierarchy of collections.

I try a bit more to isolate the problem.

In T88933#1173321, @Hans Classen (hc3d) wrote:

I have not uploaded a new file as the file is only some kB smaller without the three collections. Blender reports 3.9GB memory compared to 4.1GB with complete contents.

When you delete Blender objects, they don't always actually get deleted. There's an Orphan Data view available, from where you can purge unused stuff from the Blend file. I don't have the time to explain now, but if you Google for it, you should find some info/videos.

I can "shift" the crash a frame by joining meshes in collections. For instance, when I join the meshes in die sub collection "03_Terrace.001"

into 1 mesh

the crash happens 1 frame later, i.e. not after rendering frames 466 and 467 but after rendering frames 466, 467, and 468.

@Leon Zandman (lzandman) Cool, I just assumed that Blender would clean up stuff with no users when saving. That's why I closed Blender intermediately. Now I had a look at the orphans and purged until everything unused was gone. File size reduzed to 1GB.
Result is the same: Click Render | Render Animation and crash after having rendered frames 466 and 467.

mirandaAnimNeu8stripped.blend975 MBDownload

I can not reproduce any crash, but each frame took almost 2 minutes to render, which is quite a lot.
Not sure if this could be caused by TDR, havent seen this issue on workbench/eevee, but please try to increase timeout and check if this resolves the issue. For more details see https://docs.microsoft.com/en-us/windows-hardware/drivers/display/timeout-detection-and-recovery

Just a quick info since I have to break up now:
The TDR keys do not exist in the registry of my computer. I have added the first 3 of them and doubled the delay to 10s with no immediate difference. Maybe I have to restart my computer, which I will do later today or tomorrow.

Then I have compared the file above with the one I have used to render the complete animation at 1/4 HD on Sunday. It does not select Shadow

When I disable shadow in the settings of the above file, it renders in about 2 seconds per frame instead of 3min. At least this gives the reason (which is hard to understand for me as well) that the current render settings take almost 200 times the settings without shadow.
I will test again after restart tonight or tomorrow.

These are my settings, which I have updated:

Rendering closes the as before after frame 466.
The Windows event viewer produces the following nvidia error:

Browsing the net for this error message does not provide any useful results.
I will now try to update another nvidia driver.

Still crashing with the newest nvidia driver.
Event logger reports:

I have no idea what to test next.

Maybe you can start Blender using the --debug-all command-line argument and see if it outputs anything useful. Also, on Windows there are some debug scripts that might help: https://docs.blender.org/manual/en/latest/troubleshooting/crash.html

I don't have any experience running those.

This is the output with the debug flags:

crashlog.txt5 MBDownload

I see a nan when outputting FPS. I am wondering why the mp3 file is evaluated as I am rendering jpgs now.

I will run the debug scripts now...

I don't see anything specific when running blender_debug_gpu.cmd:

blender_system_info.txt25 KBDownload

blender_debug_output.txt1 KBDownload

Same crash with the factory script, fewer information:

blender_debug_output.txt284 BDownload

Richard Antalik (ISS) changed the task status from Needs Information from User to Needs Triage.Jun 14 2021, 12:21 AM

Workbench shadows used to be faster, see T78161: Workbench refactor causes significant performance regression with workbench shadows
But I can confirm I cannot get pass frame 467 (it is a freeze afterwards for me)

Philipp Oeser (lichtwerk) renamed this task from Crash when rendering animation in Workbench to Crash when rendering animation in Workbench (with workbench shadows).Feb 23 2022, 4:36 PM

Crash when rendering animation in Workbench (with workbench shadows)Confirmed, NormalPublicActions

Description

Related Objects

Event Timeline

Crash when rendering animation in Workbench (with workbench shadows)
Confirmed, NormalPublic
Actions