please interpret crash log #119765

Open
opened 2024-03-21 22:08:51 +01:00 by Alexander · 6 comments

System Information
Operating system: Windows 10 Pro (Version 22H2, OS build 19045.2965)
Graphics card: GeForce RTX 3060 (Driver 537.58)

Blender Version
Broken: 3.5.1

Short description of error
Random rare crash when fast working at ViewPort Shading mode(Cycles)

PS Just curious why this could happen? Its Blender, GPU driver or RAM issue?

**System Information** Operating system: Windows 10 Pro (Version 22H2, OS build 19045.2965) Graphics card: GeForce RTX 3060 (Driver 537.58) **Blender Version** Broken: 3.5.1 **Short description of error** Random rare crash when fast working at ViewPort Shading mode(Cycles) PS Just curious why this could happen? Its Blender, GPU driver or RAM issue?
Alexander added the
Priority
Normal
Type
Report
Status
Needs Triage
labels 2024-03-21 22:08:52 +01:00

Hi @AlexanderProcenko, thank you for the bug report.

From the crash log you provided, it seems that the crash is related to the subdivision modifier. One possible solution could be to disable GPU subdivision. You can do this by going to "Blender Preferences" > "Viewport" > "Subdivision".

I would also recommend upgrading to the latest GPU driver for your GeForce RTX 3060. You can find more information on troubleshooting GPU issues in Blender's official documentation: GPU Troubleshooting Documentation.

Unfortunately, I couldn't reproduce the crash using the .blend file you attached. In order to help you better, could you provide us with more information? Specifically, more detailed steps to reproduce the crash would be helpful. Without further information, it may be difficult to pinpoint the exact cause of the crash.

Hi @AlexanderProcenko, thank you for the bug report. From the crash log you provided, it seems that the crash is related to the subdivision modifier. One possible solution could be to disable GPU subdivision. You can do this by going to "Blender Preferences" > "Viewport" > "Subdivision". I would also recommend upgrading to the latest GPU driver for your GeForce RTX 3060. You can find more information on troubleshooting GPU issues in Blender's official documentation: [GPU Troubleshooting Documentation](https://docs.blender.org/manual/en/dev/troubleshooting/gpu/index.html). Unfortunately, I couldn't reproduce the crash using the .blend file you attached. In order to help you better, could you provide us with more information? Specifically, more detailed steps to reproduce the crash would be helpful. Without further information, it may be difficult to pinpoint the exact cause of the crash.
Germano Cavalcante added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2024-03-21 22:43:46 +01:00
Blender Bot added
Status
Archived
and removed
Status
Needs Information from User
labels 2024-03-24 01:06:41 +01:00
Author

@mano-wii
Hello!
Thanks you for quick reply and useful information.

In order to help you better, could you provide us with more information? Specifically, more detailed steps to reproduce the crash would be helpful. Without further information, it may be difficult to pinpoint the exact cause of the crash.

I don't remember exactly my actions. Its happens only once for me, when i quickly rotating/panning/zooming wiewport at ViewPort Shading mode and same time do picking scene objects and at the rendering process was happening in the background by F12 key.

Yes, perhaps these were not the correct actions on my side. And I needed to work more carefully. I was interested in the reason for the crash.

@mano-wii Hello! Thanks you for quick reply and useful information. > In order to help you better, could you provide us with more information? Specifically, more detailed steps to reproduce the crash would be helpful. Without further information, it may be difficult to pinpoint the exact cause of the crash. I don't remember exactly my actions. Its happens only once for me, when i quickly rotating/panning/zooming wiewport at ViewPort Shading mode and same time do picking scene objects and at the rendering process was happening in the background by F12 key. Yes, perhaps these were not the correct actions on my side. And I needed to work more carefully. I was interested in the reason for the crash.
Blender Bot added
Status
Needs Triage
and removed
Status
Archived
labels 2024-03-24 01:07:49 +01:00
Member

From the crash log you provided, it seems that the crash is related to the subdivision modifier. One possible solution could be to disable GPU subdivision. You can do this by going to "Blender Preferences" > "Viewport" > "Subdivision".

This is likely the reason. Did you check without GPU subdivision?

> From the crash log you provided, it seems that the crash is related to the subdivision modifier. One possible solution could be to disable GPU subdivision. You can do this by going to "Blender Preferences" > "Viewport" > "Subdivision". This is likely the reason. Did you check without GPU subdivision?
Pratik Borhade added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2024-03-25 04:45:09 +01:00
Author

@PratikPB2123

This` is likely the reason. Did you check without GPU subdivision?

Yes, it was turned ON, now i am checked OFF it

But why you thinking that reason is at GPU subdivision? Can you explain i am curios. Please.

@PratikPB2123 > This` is likely the reason. Did you check without GPU subdivision? Yes, it was turned ON, now i am checked OFF it But why you thinking that reason is at GPU subdivision? Can you explain i am curios. Please.
Member

crash.txt captured few function calls related to subdivision.

crash.txt captured few function calls related to subdivision.
Member

Yeah it seems that it could be some synchronization issue with subdiv. BKE_subdiv_update_from_mesh itself doesn't seem to have any particular thing that can crash, maybe it's something inside the call that broke the stack in some way, like the mesh could be null and it may crash in mesh->vert_positions(); etc.

Yeah it seems that it could be some synchronization issue with subdiv. `BKE_subdiv_update_from_mesh` itself doesn't seem to have any particular thing that can crash, maybe it's something inside the call that broke the stack in some way, like the mesh could be null and it may crash in `mesh->vert_positions();` etc.
Sign in to join this conversation.
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
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#119765
No description provided.