GUI becomes defunct in certain screen layouts #36175

Closed
opened 2013-07-17 11:16:05 +02:00 by Shannon Massman · 8 comments

%%%--- Operating System, Graphics card ---
Windows 7
NVidia GTX 660

- Blender version with error, and version that worked ---

broken: 2.68 (displays as "Blender 2.67b" v2.67.1 r57908)
working: unknown

- Short description of error ---

A screen/layout becomes corrupt, so that selecting that screen removes all GUI functionality. Blender appears to be crashed, and dragging the window leaves window repaint artifacts/patterns. However, keyboard shortcuts to switch layouts restore normal functionality. Returning to the corrupt layout reliably reproduces the problem.

- Steps for others to reproduce the error (preferably based on attached .blend file) ---

Open .blend file.
Select the "BrokenScreen" layout.

Notes:
I have had this problem on multiple .blend files. I've distilled and attached one. I have two displays. One is in portrait mode, and the other in landscape. I use screens on both simultaneously. I believe some combination of resizing/moving/entering full-screen/maximizing areas/selecting screens/deleting screens caused it, but I couldn't identify what precisely. It seems the fundamental resulting technical problem was the invalid area location/dimensions, as per screenshot.
%%%

%%%--- Operating System, Graphics card --- Windows 7 NVidia GTX 660 - Blender version with error, and version that worked --- broken: 2.68 (displays as "Blender 2.67b" v2.67.1 r57908) working: unknown - Short description of error --- A screen/layout becomes corrupt, so that selecting that screen removes all GUI functionality. Blender appears to be crashed, and dragging the window leaves window repaint artifacts/patterns. However, keyboard shortcuts to switch layouts restore normal functionality. Returning to the corrupt layout reliably reproduces the problem. - Steps for others to reproduce the error (preferably based on attached .blend file) --- Open .blend file. Select the "BrokenScreen" layout. Notes: I have had this problem on multiple .blend files. I've distilled and attached one. I have two displays. One is in portrait mode, and the other in landscape. I use screens on both simultaneously. I believe some combination of resizing/moving/entering full-screen/maximizing areas/selecting screens/deleting screens caused it, but I couldn't identify what precisely. It seems the fundamental resulting technical problem was the invalid area location/dimensions, as per screenshot. %%%

Changed status to: 'Open'

Changed status to: 'Open'

%%%Hi Shannon, I checked the file and can confirm that there is a corrupt screen layout, but (mostly) on its own this isn't enough to fix the bug.

We need to know how it became corrupt - the steps to redo creation of a corrupt screen, so we can prevent it from happening in future.

If we cant redo the bug its possible the data became corrupt some other way (bad memory, disk sector etc) - and we can't support this kind of corruption well.%%%

%%%Hi Shannon, I checked the file and can confirm that there is a corrupt screen layout, but (mostly) on its own this isn't enough to fix the bug. We need to know how it became corrupt - the steps to redo creation of a corrupt screen, so we can prevent it from happening in future. If we cant redo the bug its possible the data became corrupt some other way (bad memory, disk sector etc) - and we can't support this kind of corruption well.%%%

%%%I understand, and I'll keep trying to correlate it to events.

I'm more likely to push the envelope on the type of operations that caused this, and track down the defect, if there is a fairly straightforward way to remove the corrupt screens from my .blend. Does "bpy.data.screens['BrokenScreen'].user_clear()" make sense for this?
%%%

%%%I understand, and I'll keep trying to correlate it to events. I'm more likely to push the envelope on the type of operations that caused this, and track down the defect, if there is a fairly straightforward way to remove the corrupt screens from my .blend. Does "bpy.data.screens['BrokenScreen'].user_clear()" make sense for this? %%%

%%%This worked for me to delete it, so I'll try occasionally to break my working documents.%%%

%%%This worked for me to delete it, so I'll try occasionally to break my working documents.%%%

%%%closing this report since we need steps to redo bugs.
please make a new report with steps to redo if you manage to find the cause.

%%%

%%%closing this report since we need steps to redo bugs. please make a new report with steps to redo if you manage to find the cause. %%%

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

%%%I filed a new report with the steps to reproduce this. It's #36652.

Meanwhile, I need a way to remove the defunct screens. Somehow user_clear() doesn't work on them. The user count resets to zero but the screens are still in the blend after saving and reloading. I can't seem to find any another way to get rid of them via UI or python.%%%

%%%I filed a new report with the steps to reproduce this. It's #36652. Meanwhile, I need a way to remove the defunct screens. Somehow user_clear() doesn't work on them. The user count resets to zero but the screens are still in the blend after saving and reloading. I can't seem to find any another way to get rid of them via UI or python.%%%

%%%Ok, I've managed to partially solve the problem with deleting corrupt screen layouts by assigning a keyboard shortcut to bpy.ops.screen.delete() but it only worked for three of the five corrupt layouts I had in the blend. Somehow the remaining two don't let the command go through even though they react to Ctrl+Right/Left Arrow as expected. Hopefully that helps someone else if they come across this issue.%%%

%%%Ok, I've managed to partially solve the problem with deleting corrupt screen layouts by assigning a keyboard shortcut to bpy.ops.screen.delete() but it only worked for three of the five corrupt layouts I had in the blend. Somehow the remaining two don't let the command go through even though they react to Ctrl+Right/Left Arrow as expected. Hopefully that helps someone else if they come across this issue.%%%
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
3 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#36175
No description provided.