Guaranteed Crash in Edit Mode Since 3.5 #106454

Closed
opened 2023-04-02 13:59:54 +02:00 by Franhound · 6 comments

System Information
Operating system: Linux-5.15.0-69-generic-x86_64-with-glibc2.35 64 Bits
Graphics card: Mesa Intel(R) HD Graphics 3000 (SNB GT2) Intel 3.3 (Core Profile) Mesa 22.3.5 (git-6570a15662)

Blender Version
Broken: version: 3.5.0, branch: blender-v3.5-release, commit date: 2023-03-29 02:56, hash: 1be25cfff18b
Worked: (newest version of Blender that worked as expected)

Short description of error
Blender 3.5 is guaranteed to crash/close down when I try to go to Edit Mode when a curve is selected.

Exact steps for others to reproduce the error

  1. Create any new Blender project.
  2. Add any curve, Bezier or otherwise
  3. Go to edit mode.

Then Blender would crash immediately after that. It happens with any .blend file for me.

  • Blender 3.5 is guaranteed to crash/close down when I try to go to Edit Mode when a curve is selected.
  • Only happens with curves.
  • Only happens in 3.5.
  • Everything else runs smoothly.
  • Happens with any .blend file. Even a nice, empty one. Will send a screen recording if necessary.
**System Information** Operating system: Linux-5.15.0-69-generic-x86_64-with-glibc2.35 64 Bits Graphics card: Mesa Intel(R) HD Graphics 3000 (SNB GT2) Intel 3.3 (Core Profile) Mesa 22.3.5 (git-6570a15662) **Blender Version** Broken: version: 3.5.0, branch: blender-v3.5-release, commit date: 2023-03-29 02:56, hash: `1be25cfff18b` Worked: (newest version of Blender that worked as expected) **Short description of error** Blender 3.5 is guaranteed to crash/close down when I try to go to Edit Mode when a curve is selected. **Exact steps for others to reproduce the error** 1. Create any new Blender project. 2. Add any curve, Bezier or otherwise 3. Go to edit mode. Then Blender would crash immediately after that. It happens with any .blend file for me. - Blender 3.5 is guaranteed to crash/close down when I try to go to Edit Mode when a curve is selected. - Only happens with curves. - Only happens in 3.5. - Everything else runs smoothly. - Happens with any .blend file. Even a nice, empty one. Will send a screen recording if necessary.
Franhound added the
Priority
Normal
Type
Report
Status
Needs Triage
labels 2023-04-02 13:59:54 +02:00
Member

This seems to be a duplicate of #106432.

Note that both of reported graphics hardware (Here being Mesa Intel(R) HD Graphics 3000 (SNB GT2) Intel 3.3 (Core Profile) Mesa 22.3.5) seems to be unsupported for blender 3.5.

This seems to be a duplicate of #106432. Note that both of reported graphics hardware (Here being `Mesa Intel(R) HD Graphics 3000 (SNB GT2) Intel 3.3 (Core Profile) Mesa 22.3.5`) seems to be unsupported for blender 3.5.
Blender Bot added
Status
Archived
and removed
Status
Needs Triage
labels 2023-04-02 16:53:35 +02:00
Author

This seems to be a duplicate of #106432.

Note that both of reported graphics hardware (Here being Mesa Intel(R) HD Graphics 3000 (SNB GT2) Intel 3.3 (Core Profile) Mesa 22.3.5) seems to be unsupported for blender 3.5.

Aww. So is that it? Starting from 3.5 onwards, I will not be able to use Blender in this machine anymore? That's a shame because aside from this crash, everything else runs so smoothly. And pretty fast, too. Are there no workarounds I can do to avoid these crashes?

> This seems to be a duplicate of #106432. > > Note that both of reported graphics hardware (Here being `Mesa Intel(R) HD Graphics 3000 (SNB GT2) Intel 3.3 (Core Profile) Mesa 22.3.5`) seems to be unsupported for blender 3.5. Aww. So is that it? Starting from 3.5 onwards, I will not be able to use Blender in this machine anymore? That's a shame because aside from this crash, everything else runs so smoothly. And pretty fast, too. Are there no workarounds I can do to avoid these crashes?
Member

I don't think there is much you can do rn, maybe the developers can actually take a look at those shader problems and try to make them as adaptable to older GL versions as possible, but I'm not sure that's gonna be the priority, because that kind of change would involve the design of the graphics backend.

Here you can check for Mesa features for different generations of integrated graphics: https://wiki.gentoo.org/wiki/Intel#Feature_support

I don't think there is much you can do rn, maybe the developers can actually take a look at those shader problems and try to make them as adaptable to older GL versions as possible, but I'm not sure that's gonna be the priority, because that kind of change would involve the design of the graphics backend. Here you can check for Mesa features for different generations of integrated graphics: https://wiki.gentoo.org/wiki/Intel#Feature_support
Author

I don't think there is much you can do rn, maybe the developers can actually take a look at those shader problems and try to make them as adaptable to older GL versions as possible, but I'm not sure that's gonna be the priority, because that kind of change would involve the design of the graphics backend.

Here you can check for Mesa features for different generations of integrated graphics: https://wiki.gentoo.org/wiki/Intel#Feature_support

I see. Thank you for the information. I'm still hoping it gets fixed, seeing as everything else seems to be working fine. :'/

> I don't think there is much you can do rn, maybe the developers can actually take a look at those shader problems and try to make them as adaptable to older GL versions as possible, but I'm not sure that's gonna be the priority, because that kind of change would involve the design of the graphics backend. > > Here you can check for Mesa features for different generations of integrated graphics: https://wiki.gentoo.org/wiki/Intel#Feature_support I see. Thank you for the information. I'm still hoping it gets fixed, seeing as everything else seems to be working fine. :'/
Member

Hi @Franhound this might get fixed, see #106432.

Hi @Franhound this might get fixed, see #106432.
Author

Hi @Franhound this might get fixed, see #106432.

Aww, yay. That would be awesome! Thank you for the heads-up!

> Hi @Franhound this might get fixed, see #106432. Aww, yay. That would be awesome! Thank you for the heads-up!
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
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#106454
No description provided.