Blender crashes randomly when rendering animation (EXCEPTION_ACCESS_VIOLATION) #126585

Closed
opened 2024-08-21 10:24:51 +02:00 by Vincent-Abert-4 · 5 comments

System Information
Operating system: Windows 11
Graphics card: NVIDIA GeForce RTX 4070 Ti SUPER/PCIe/SSE2

Blender Version
Broken: 4.2.1 LTS, branch: blender-v4.2-release, commit date: 2024-08-19 11:21, hash: 396f546c9d, type: Release
Worked: Couldn't try earlier versions because of addons/scene compatibility
Short description of error

When I render this project's animations, it randomly crashes, sometimes after 5 frames, sometimes after 40.
I tried reinstalling Blender, reinstalling NVIDIA drivers, switching between studio and game drivers, nothing seems to fix it.

Exact steps for others to reproduce the error
I can not share the full file right now as it is quite heavy and uses a couple of addons, but I will try to reduce it to a simple file that still crashes... In the meantime I was wondering whether some people who are more comfortable with Blender logs could identify the issue thanks to the crash report.

Here are the lines that seem to outline the crash (full files are linked to this ticket) :

From the debug log file

I0821 10:17:03.572546 34072 device.cpp:541] Mapped host memory limit set to 64,175,448,064 bytes. (59.77G)
I0821 10:17:03.629052 34072 device_impl.cpp:63] Using AVX2 CPU kernels.
Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF780F3E65C
Module : blender.exe
Thread : 00007f64

From the crash report

ExceptionCode : EXCEPTION_ACCESS_VIOLATION
Exception Address : 0x00007FF780F3E65C
Exception Module : blender.exe
Exception Flags : 0x00000000
Exception Parameters : 0x2
Parameters[0] : 0x0000000000000000
Parameters[1] : 0x00000000000000D7

Stack trace:
blender.exe :0x00007FF780F3E640 blender::draw::DRW_mesh_batch_cache_validate
blender.exe :0x00007FF780F08C00 drw_engines_cache_populate
blender.exe :0x00007FF780F04240 DRW_draw_render_loop_2d_ex
blender.exe :0x00007FF781B58770 image_main_region_draw
blender.exe :0x00007FF7812EFC90 ED_region_do_draw
blender.exe :0x00007FF780E04290 wm_draw_window_offscreen
blender.exe :0x00007FF780E040C0 wm_draw_window
blender.exe :0x00007FF780E03AF0 wm_draw_update
blender.exe :0x00007FF780DCB700 WM_main
blender.exe :0x00007FF780788160 main
blender.exe :0x00007FF783194934 __scrt_common_main_seh
KERNEL32.DLL :0x00007FFA6DE82560 BaseThreadInitThunk
ntdll.dll :0x00007FFA6F20AF00 RtlUserThreadStart

This is really driving me crazy, hopefully someone can help. Thank you !

**System Information** Operating system: Windows 11 Graphics card: NVIDIA GeForce RTX 4070 Ti SUPER/PCIe/SSE2 **Blender Version** Broken: 4.2.1 LTS, branch: blender-v4.2-release, commit date: 2024-08-19 11:21, hash: 396f546c9d82, type: Release Worked: Couldn't try earlier versions because of addons/scene compatibility **Short description of error** When I render this project's animations, it randomly crashes, sometimes after 5 frames, sometimes after 40. I tried reinstalling Blender, reinstalling NVIDIA drivers, switching between studio and game drivers, nothing seems to fix it. **Exact steps for others to reproduce the error** I can not share the full file right now as it is quite heavy and uses a couple of addons, but I will try to reduce it to a simple file that still crashes... In the meantime I was wondering whether some people who are more comfortable with Blender logs could identify the issue thanks to the crash report. Here are the lines that seem to outline the crash (full files are linked to this ticket) : From the debug log file I0821 10:17:03.572546 34072 device.cpp:541] Mapped host memory limit set to 64,175,448,064 bytes. (59.77G) I0821 10:17:03.629052 34072 device_impl.cpp:63] Using AVX2 CPU kernels. Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FF780F3E65C Module : blender.exe Thread : 00007f64 From the crash report ExceptionCode : EXCEPTION_ACCESS_VIOLATION Exception Address : 0x00007FF780F3E65C Exception Module : blender.exe Exception Flags : 0x00000000 Exception Parameters : 0x2 Parameters[0] : 0x0000000000000000 Parameters[1] : 0x00000000000000D7 Stack trace: blender.exe :0x00007FF780F3E640 blender::draw::DRW_mesh_batch_cache_validate blender.exe :0x00007FF780F08C00 drw_engines_cache_populate blender.exe :0x00007FF780F04240 DRW_draw_render_loop_2d_ex blender.exe :0x00007FF781B58770 image_main_region_draw blender.exe :0x00007FF7812EFC90 ED_region_do_draw blender.exe :0x00007FF780E04290 wm_draw_window_offscreen blender.exe :0x00007FF780E040C0 wm_draw_window blender.exe :0x00007FF780E03AF0 wm_draw_update blender.exe :0x00007FF780DCB700 WM_main blender.exe :0x00007FF780788160 main blender.exe :0x00007FF783194934 __scrt_common_main_seh KERNEL32.DLL :0x00007FFA6DE82560 BaseThreadInitThunk ntdll.dll :0x00007FFA6F20AF00 RtlUserThreadStart This is really driving me crazy, hopefully someone can help. Thank you !
Vincent-Abert-4 added the
Severity
Normal
Status
Needs Triage
Type
Bug
labels 2024-08-21 10:24:52 +02:00
Iliya Katushenock added the
Interest
Viewport & EEVEE
label 2024-08-21 20:20:34 +02:00
Member

Hi, thanks for the report. From logs, crash seems file specific. In your file, some link libraries are also there. Could you attach simplified version of file where crash can be reproduced?

BTW, how much RAM/VRAM system have? And how much is utilized during the render?

Hi, thanks for the report. From logs, crash seems file specific. In your file, some link libraries are also there. Could you attach simplified version of file where crash can be reproduced? BTW, how much RAM/VRAM system have? And how much is utilized during the render?
Pratik Borhade added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2024-08-23 09:56:14 +02:00

Hi, thanks for the report. From logs, crash seems file specific. In your file, some link libraries are also there. Could you attach simplified version of file where crash can be reproduced?

BTW, how much RAM/VRAM system have? And how much is utilized during the render?

Hi, thank you for the reply. I do have quite a few linked libraries indeed. I spent hours disabling and enabling collections in order to find the culprit, but I didn't get any result, as the project can sometimes render hundreds of frame before crashing, which makes it very impractical, if not completely impossible to figure out...

I have 64 GB RAM and 16 GB of VRAM, and the renders' memory is generally around 15 000M. VRAM limitation was my first instinct, but I managed to reproduce the crash even on a simplified version of the scene, with barely 10 000M of memory being used.

I really can't justify spending more days on this, sadly, but I have found a solution that seem to work so far : rendering through a command line, without interface, no crash occurs

> Hi, thanks for the report. From logs, crash seems file specific. In your file, some link libraries are also there. Could you attach simplified version of file where crash can be reproduced? > > BTW, how much RAM/VRAM system have? And how much is utilized during the render? Hi, thank you for the reply. I do have quite a few linked libraries indeed. I spent hours disabling and enabling collections in order to find the culprit, but I didn't get any result, as the project can sometimes render hundreds of frame before crashing, which makes it very impractical, if not completely impossible to figure out... I have 64 GB RAM and 16 GB of VRAM, and the renders' memory is generally around 15 000M. VRAM limitation was my first instinct, but I managed to reproduce the crash even on a simplified version of the scene, with barely 10 000M of memory being used. I really can't justify spending more days on this, sadly, but I have found a solution that seem to work so far : rendering through a command line, without interface, no crash occurs
Member

Thanks. Image editor redraw triggered the crash, that suggests why command line interface is working.
Possibly mesh.runtime->batch_cache has garbage memory.

I managed to reproduce the crash even on a simplified version of the scene, with barely 10 000M of memory being used.

Can you share logs and .blend of above?

Run following script to validate if any mesh data is corrupted (likely unrelated as command line render is good)?
Check console for error(s): Window > Toggle System Console

for ob in bpy.data.objects:
    if ob.type == "MESH":
        if ob.data.validate():
            print(ob.name + " corrupted")
Thanks. Image editor redraw triggered the crash, that suggests why command line interface is working. Possibly `mesh.runtime->batch_cache` has garbage memory. > I managed to reproduce the crash even on a simplified version of the scene, with barely 10 000M of memory being used. Can you share logs and .blend of above? Run following script to validate if any mesh data is corrupted (likely unrelated as command line render is good)? Check console for error(s): `Window > Toggle System Console` ``` for ob in bpy.data.objects: if ob.type == "MESH": if ob.data.validate(): print(ob.name + " corrupted") ```
Member
@Vincent-Abert-4 ^
Member

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed. Thanks again for the report. If the problem persists please open a new report with the required information.
Blender Bot added
Status
Archived
and removed
Status
Needs Information from User
labels 2024-11-28 09:36:07 +01:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Asset System
Module
Asset System
Module
Core
Module
Development Management
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#126585
No description provided.