Regression: Join Area in causes crashes in some cases #43714

Closed
opened 2015-02-17 20:59:31 +01:00 by Zauber Paracelsus · 23 comments

System Information
64bit Manjaro Linux, kernel 3.14.32
CPU: AMD Phenom II 970 Deneb quad-core
GPU: nVidia GTX 650 Ti, driver 343.36

Blender Version
Broken: 2.73 691cb61
Worked: 2.73 b4d8fb5

Short description of error
Yay, fourth post-2.73 crash I've found! This bug is very simple and repros with 100% consistency on my system. What happens is if I use Split Area on the UV/Image Editor and then undo it by Join Area, blender instantly crashes.

A second instance where a crash results is doing Split Area on any pane, and then opening another file or reopening the current one.

Perhaps something in the UI is getting corrupted?

Exact steps for others to reproduce the error

Case 1:

  1. Set any viewport panel to UV/Image Editor
  2. Use the Split Area function on the UV/Image Editor panel
  3. Use the Join Area function on the UV/Image Editor panel
  4. Crash!

Case 2:

  1. Use the Split Area function on any panel in the viewport
  2. Reload the current file or load a different one.
  3. Crash!

Crash Log: blender.crash.txt

**System Information** 64bit Manjaro Linux, kernel 3.14.32 CPU: AMD Phenom II 970 Deneb quad-core GPU: nVidia GTX 650 Ti, driver 343.36 **Blender Version** Broken: 2.73 691cb61 Worked: 2.73 b4d8fb5 **Short description of error** Yay, fourth post-2.73 crash I've found! This bug is very simple and repros with 100% consistency on my system. What happens is if I use Split Area on the UV/Image Editor and then undo it by Join Area, blender instantly crashes. A second instance where a crash results is doing Split Area on *any* pane, and then opening another file or reopening the current one. Perhaps something in the UI is getting corrupted? **Exact steps for others to reproduce the error** Case 1: 1) Set any viewport panel to UV/Image Editor 2) Use the Split Area function on the UV/Image Editor panel 3) Use the Join Area function on the UV/Image Editor panel 4) Crash! Case 2: 1) Use the Split Area function on any panel in the viewport 2) Reload the current file or load a different one. 3) Crash! **Crash Log:** [blender.crash.txt](https://archive.blender.org/developer/F144326/blender.crash.txt)

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @ZauberParacelsus

Added subscriber: @ZauberParacelsus
Member

Added subscriber: @JulianEisel

Added subscriber: @JulianEisel
Member

Cannot recreate that here. Could you run the softwaregl bundled with Blender? This will be quite slow, but shows us if this is a gpu driver issue or not.

Cannot recreate that here. Could you run the softwaregl bundled with Blender? This will be quite slow, but shows us if this is a gpu driver issue or not.

Still occurs with softwaregl. What OS were you using, and was it 32bit or 64bit?

Still occurs with softwaregl. What OS were you using, and was it 32bit or 64bit?

Added subscriber: @ideasman42

Added subscriber: @ideasman42

@ZauberParacelsus

Please include exact steps to redo the bug, starting from factory settings.

I tested splitting & joining image & render windows many times, works fine here.

@ZauberParacelsus Please include exact steps to redo the bug, starting from factory settings. I tested splitting & joining image & render windows many times, works fine here.

@ideasman42 Issue does not repro from factory reset. However, after a factory reset, the issue repros again when I load up my old default blender scene.

May have more luck performing the repro steps above with it: startup.blend

@ideasman42 Issue does not repro from factory reset. However, after a factory reset, the issue repros again when I load up my old default blender scene. May have more luck performing the repro steps above with it: [startup.blend](https://archive.blender.org/developer/F144357/startup.blend)

Further note, I do not know what steps, if any, are required in order to redo the bug. The issue came out of nowhere, but does not occur in 2.73 release, and the startup.blend I supplied has not been modified since November 29th.

Further note, I do not know what steps, if any, are required in order to redo the bug. The issue came out of nowhere, but does not occur in 2.73 release, and the startup.blend I supplied has not been modified since November 29th.

@ZauberParacelsus, please include steps to redo the bug from the startup.blend linked above.

@ZauberParacelsus, please include steps to redo the bug from the `startup.blend` linked above.

I already put repro steps above in the initial report.

I already put repro steps above in the initial report.
Member

Still not able to reproduce that here. You build Blender on your own, right? So you could test with latest master or buildbot builds to see if the issue is present in them. Also please make sure you are not in debug mode (CMAKE_BUILD_TYPE must be set to Release)

Still not able to reproduce that here. You build Blender on your own, right? So you could test with latest master or [buildbot ](https://builder.blender.org/download/) builds to see if the issue is present in them. Also please make sure you are not in debug mode (CMAKE_BUILD_TYPE must be set to Release)

Ran steps (Case 1 & Case 2), cant redo this.

Moving this to unconfirmed

Ran steps (Case 1 & Case 2), cant redo this. Moving this to **unconfirmed**

@JulianEisel: I used one of the buildbot builds for testing this one.

@JulianEisel: I used one of the buildbot builds for testing this one.

Since the issue will not repro for any developers, I am compiling a debug build of blender so that I can obtain a backtrace through gdb.

Since the issue will not repro for any developers, I am compiling a debug build of blender so that I can obtain a backtrace through gdb.

Okay, got the backtraces.

This one is for when simply splitting a panel and reloading the file: T43714_backtrace_1.txt

This one is for when splitting a UV/Texture Edit panel and then joining it: T43714_backtrace_2.txt

Okay, got the backtraces. This one is for when simply splitting a panel and reloading the file: [T43714_backtrace_1.txt](https://archive.blender.org/developer/F144393/T43714_backtrace_1.txt) This one is for when splitting a UV/Texture Edit panel and then joining it: [T43714_backtrace_2.txt](https://archive.blender.org/developer/F144394/T43714_backtrace_2.txt)

@ZauberParacelsus

I'm not sure what splitting a panel even means (panels can only be collapsed), please give exact and detailed steps.

Splitting and joining windows is a common operation. If it only fails on your computer, its possibly not even a bug in Blender. (possibly a corrupt blend file for example).

This is why we ask if you can redo from factory startup.

@ZauberParacelsus I'm not sure what splitting a panel even means (panels can only be collapsed), please give exact and detailed steps. Splitting and joining windows is a common operation. If it only fails on your computer, its possibly not even a bug in Blender. (possibly a corrupt blend file for example). This is why we ask if you can redo from factory startup.

I don't even know what the correct name is. Area, I guess? When I was talking about panels, I was referring to things like 3D View, Timeline, and UV/Image Editor.

I don't even know what the correct name is. Area, I guess? When I was talking about panels, I was referring to things like 3D View, Timeline, and UV/Image Editor.

Added subscriber: @Psy-Fi

Added subscriber: @Psy-Fi

Nope, can't reproduce here either...

Nope, can't reproduce here either...

It's probably the userpref that has the issue, it may even be an erratic add-on. Can you try changing options in your user preferences and test which one causes the issue?

It's probably the userpref that has the issue, it may even be an erratic add-on. Can you try changing options in your user preferences and test which one causes the issue?

This issue can be closed for now. It no longer occurs under the current builds from buildbot, fda1198

This issue can be closed for now. It no longer occurs under the current builds from buildbot, fda1198

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Antonis Ryakiotakis self-assigned this 2015-02-18 18:23:59 +01:00
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#43714
No description provided.