Material preview and rendered buttons crashes the program. #101675
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
11 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#101675
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
Operating system: Windows-10-10.0.22000-SP0 64 Bits
Blender Version
Broken: version: 3.3.1, branch: master, commit date: 2022-10-04 18:35, hash:
b292cfe5a9Worked: (newest version of Blender that worked as expected)
Short description of error
Material preview and rendered buttons top right crashes the program.
Apparently the problem happens because the
closure_evalfunction already has a body:blender_debug_output.txt
Exact steps for others to reproduce the error
Added subscriber: @thisisananimator1
#103892 was marked as duplicate of this issue
#103665 was marked as duplicate of this issue
#102546 was marked as duplicate of this issue
#102416 was marked as duplicate of this issue
#102099 was marked as duplicate of this issue
#102069 was marked as duplicate of this issue
Added subscriber: @ThomasDinges
Changed status from 'Needs Triage' to: 'Needs User Info'
Cannot confirm a crash with latest master and a AMD 5500 XT.
Please open Blender's installation directory and double click on the
blender_debug_gpu.cmd. This will start Blender in debug mode and create log files. Try to reproduce the error again. Once it crashes or you close Blender manually the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located inC:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt(or simply type%TEMP%into the path bar of the Windows Explorer).blender_system_info.txt
blender_debug_output.txt
after crash these were the two files that we got. I couldn't figure out how to find the crash log though. The reports that I'm sending are from the crash that happened when I pressed material preview. Three more problems occur with this crash. The rendered button top right next to material preview, the 2d animation tab doesn't work, and the shading tab closes it out too.
Changed status from 'Needs User Info' to: 'Needs Triage'
Added subscriber: @fclem
Thanks for the files. @fclem Hey, Is the log provided helpful? It contains an error on top:
ERROR (gpu.debug): : GL_INVALID_FRAMEBUFFER_OPERATION : Cubemap Workaround End9The crash itself is caused by the compilation failing. Try to run with
--debug-gpu-force-workarounds.Added subscriber: @OmarEmaraDev
Changed status from 'Needs Triage' to: 'Needs User Info'
Can you redo the steps above but with the
blender_debug_gpu_glitchworkaround.cmdfile instead?Added subscriber: @Chillibeen
Added subscriber: @persun
Added subscribers: @LilChins, @LazyDodo, @PratikPB2123
Crashto Material preview and rendered buttons crashes the program.Omar, I didn't see a response to your message. Since I have the same problem I did it with my pc. This is what I got when I chose the glitchworkaround
blender_system_info.txt
blender_debug_output.txt
Hope this helps!!
Changed status from 'Needs User Info' to: 'Needs Triage'
Added subscriber: @mano-wii
Changed status from 'Needs Triage' to: 'Needs User Info'
The last log revealed the compilation error:
Apparently the problem happens because the
closure_evalfunction already has a body.But this report is still missing the steps to reproduce the problem.
Does this crash happen with any file?
I have found that It crashes when I try to open a 2D Animation file.
Is there more or different information that is needed?
Any 2D Animation file or would it be some specific file?
A guideline for making bug reports can be found at https://wiki.blender.org/wiki/Process/Bug_Reports
Any file. I start up blender and select 2D animation file. It then shuts down. But not to any specific file. Ive tried to open different 3D animation files and it crashes when I do the steps.
The 2D Animation template starts with Viewport Shading mode, so I think this is probably not about 2D Animation template but EEVEE.
Personally I don't experience any crash (Windows 10, RX570, driver: 22.10.1 & 22.11.1) but my report about volume artifact (#102099) was merged into this. Still not sure how these are related though.
Actually, looking at system info files (F13892502, F13769759, F13643912) everyone here experiencing the crash is using driver version 22.20.16. I guess this is for newer cards?
Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'
I've updated the description, it seems to be enough information.
All that remains now is to test other versions of Blender. Preferably the latest daily build:
https://builder.blender.org/download/
And as this seems like a graphic driver issue. Please double-check if the drivers are up to date.
To upgrade to the latest driver, see here for more information: https://docs.blender.org/manual/en/dev/troubleshooting/gpu/index.html
Added subscriber: @Phillipe-L
that seemed to work. updating my driver solved the problem. Thanks!
Updating drivers did in fact solve my problem! For anyone else having future problems, I DID NOT go to the drivers on my computer and click "update drivers" because in many cases that will tell you that the drivers are already up to date. I went to my product makers website and downloaded the latest graphic drivers and processor updates from there. its a common mix up, thankfully Germano gives a link to the different product maker websites so use that, hope this helps.
Added subscribers: @That1Guy592, @EAW
Added subscriber: @PreparedSoap
Changed status from 'Needs Developer To Reproduce' to: 'Resolved'
From multiple comments It seems upgrading drivers has fixed the crash. I'll close this ticket for now. If problem persists. feel free to comment or reopen the report.