Blender is crashing instantly to the desktop randomly (solid viewport) #101696
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
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, Assets & 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
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
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
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#101696
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
OS: Windows 10 Pro 64bit (Version 21H2, OS Build 19044.2006)
GPU: Nvidia GeForce RTX 2070 (Driver: Version 517.48 (released 27th September 2022))
CPU: AMD Ryzen 7 2700
RAM: 64GB
Blender Version
Broken: version: 3.3 (and versions for the last couple of years)
Worked: none since 2020 approx.
Short description of error
Blender crashes seemingly randomly when performing modelling actions such as moving vertices, clicking sliders or buttons, switching to wireframe view, or moving the viewport camera in any way. There may be other actions that cause crashes. Crashes cause Blender to instantly close to desktop, leaving no crash dumps. Crashes occurring over multiple versions since 2020, multiple reinstallations of the OS, and clean reinstallations of graphics driver.
Using blender_debug_gpu.cmd, I was able to retrieve a log from a crash that has some differences to a normal log:
"INFO (gpu.debug): Notification : Buffer usage warning: Analysis of buffer object 82 (bound to GL_SHADER_STORAGE_BUFFER (1)) usage indicates that the GPU is the primary producer and consumer of data for this buffer object. The usage hint supplied with this buffer object, GL_STATIC_DRAW, is inconsistent with this usage pattern. Try using GL_STREAM_COPY_ARB, GL_STATIC_COPY_ARB, or GL_DYNAMIC_COPY_ARB instead."
Currently, have no way to reproduce the crashes at will, they just seem to happen during my normal work. Load tests using OCCT do not cause crashes.
Debug log from crash:
blender_debug_output2.txt
Normal debug log:
blender_debug_output_normal.txt
Added subscriber: @KungFuCactus
Added subscriber: @OmarEmaraDev
Changed status from 'Needs Triage' to: 'Needs User Info'
Could you maybe look at the Window Event Viewer once Blender crashes and see if there are any relevant events like GPU timeouts or resets?
Do you notice any unusual system resource utilization? In particular, does RAM usage get unusually high?
Can you try
blender_debug_gpu_glitchworkaround.cmdand see if it crashes with that?Thank you, I'll try doing that, but I have no way to actually trigger, or predict a crash, they occur randomly, and sometimes there are days between them. I'll let you know if I find anything. Until then, please don't close this task.
Also, during the crashes, I have not noticed any unusual resource utilisation, I'll try to keep a look-out, but the crashes are really fast and difficult to react to.
Okay, no worries, we will wait for your report.
Hey, just remembered I took some dates and times for a few of the crashes. I checked the Event Viewer for anything suspicious happening at those times, and I couldn't see anything. The only thing odd I noticed was that there were large stretches of time on some days when nothing was reported on the event viewer. For example, on 01/10/22 from 09:07am, nothing is reported to the event viewer until 20:12pm, whereas most other days do not such large gaps.
hmmm, okay. But I would still double check next time the crash happens just for completeness.
Hey, just wanted to update that it has been 15 days without a crash, and today I just had one. I tried to enter wireframe view with multiple high-poly models with subdiv modifiers enabled, and it instantly crashed to desktop. Unfortunately, I forgot to use the gpu_workaround.cmd. In this session, I'm not sure if there's any connection between using the workaround and stopping the crashes. Also, I had another theory that turning off “Limit Surface” in my subdiv modifiers had stopped the crashing, but that appears to be incorrect now. There's nothing in WhoCrashed or the Event Viewer Anyway, I'll keep going and try to get something.
It is possible that the GPU workarounds file can stop the crashes. But it would be good to try to confirm that by noting if Blender ever crashed with it.
Hey, so I finally had another crash while I was making some materials in the shader editor and got a debug file from the gpu_workaround this time. blender_debug_output_GPU-Debug-Crash.txt
Changed status from 'Needs User Info' to: 'Needs Triage'
Hey, got another crash log for you. It happened when I pressed save on an image I rendered, rendering had completed, I was in solid viewport.
Also, I was wondering if there was any new information about this situation. I'm not exactly sure what “Needs Triage” means in this case.
blender_debug_output_Crash2.txt
Hey, so I just tried to launch Blender again after the crash and I noticed it won't start. The window appears for a second, then instantly closes. This is the case with both a normal non-debug launch and the GPU debug command. A debug file is created, but there's no text. I'll include it anyway, just in case.blender_system_info_BlenderNotStarting.txt
blender_debug_output_BlenderNotStarting.txt
Added subscriber: @PratikPB2123
Changed status from 'Needs Triage' to: 'Needs User Info'
Hi, could be possible that this is similar to {#100620}?
Could you restore GPU settings and try to repro the crash again?
Hey, sorry took so long to respond, didn't get notified. Anyway, had a look through #100620, looks a lot like my issue. The OP from #100620 was able to provide stack traces, which I don't know how to get, but I have been using the gpu_glitch_workaround debug, and today I got another debug output from it.
This time, I was using the viewport render image option, and also trying to save the resulting image. The viewport render didn't crash every time, it also didn't crash every time I tried to save the image.
In the debug output, there are several warnings about recompiling bases on GL state.
Also, what do you mean by restoring GPU settings? Do you mean the actual driver settings, or something in Blender? I've turned off GPU subdivision under the preferences now, I'll keep going and see if I can get another crash report.
Had another crash when I pressed find missing files button.
I was just trying to figure out how to get the stack trace to post here, but it seems it only appears if there is a debug log. In my case, because Blender instantaneously crashes to the desktop, there is no debug_log.txt file available. All that's in the folder when Blender crashes while using the gpu_debug_workaround.cmd is the debug_output.txt and system_info.txt.
Since yesterday, I have begun experiencing a new symptom. After a crash, I can't reopen Blender unless I fully restart my computer. This was occurring in 3.3 and now in 3.4. Also had another crash with a log from the gpu_workaround.cmd.
Just had a crash on a completely clean installation of Blender (with addons enabled (although even completely default Blender would still crash). I was running this time without the debug command to see if I could restart Blender afterward – I can't.
At this point, even the triggers for a crash are completely unclear. At first, it used to be just going between the viewport modes (wireframe, x-ray, solid), but now it seems to happen for basically anything I do completely randomly. In this case, clicked the preferences button and it crashed.
Hey, yesterday I installed an older GPU, an Nvidia 750TI and did a clean reinstallation of the drivers using DDU. I also did a clean reinstallation of Blender 3.4, but today I have had another crash in exactly the same way as previously described: instantly crashing to desktop.
Please advise on next steps to take for troubleshooting. I use Blender professionally and the mounting problems are making it highly difficult to continue, especially having to restart my computer after each crash. Currently, I cannot give any more information unless directed.
Hey, I have same issue, try to restart explorer.exe, or kill crashhandler.exe.
I found that Blender is attached to explorer.exe, maybe restarting that would help.
There any logs in event viewer after crash - and crashing is often caused by opening something where we can see file dialog.
Hey, thanks for the reply. I'll try your suggestion when the next crash occurs and see if I can restart then. Also, I'm not sure if I understood the last part correctly, did you mean to ask if there are any crash logs in the event viewer, because after previous crashes nothing has appeared in the event viewer.
Hey, sorry - badly wrote. I meaned - I can't see any informations about crashes in event viewer as you! :)
Ah, I see. Thank you for clarifying.