UV/Image Editor breaks on mode change + undo #34866

New Issue

Bjørnar Frøyse · 2013-04-04T15:00:15+02:00

Bjørnar Frøyse commented

2013-04-04 15:00:15 +02:00

%%%--- Operating System, Graphics card ---

Windows 7 64bit, Geforce 560ti

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

Successfully repeated in 2.66.5 r55767

And was actually able to reproduce this in 2.49b... Wow.

- Short description of error ---

Assigning a texture to selected faces, then doing a certain pattern of mode switching and undoing will either break the UV/image editor or crash Blender.
Screenshot of the error (with console errors visible too) is attached.

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

Open attached .blend file
Enter edit mode
Make sure all faces are selected
Assign a new image to the mesh (click New in the image editor)
Enter object mode
Undo (So the texture disappears from the image editor view)
Enter edit mode
Undo

The image editor should now look like it does in the attached screenshot.

This has not been 100% repeatable, but it happens more often than not. If nothing happens after step 8, repeat from step 5.

Sometimes Blender will even crash completely (quick exit, no error or crash dialog given) when returning to object mode, even if the image editor doesn't visually break.

Console outputs this error (among others):

Traceback (most recent call last):

File "C:\Program Files\Blender Foundation\Blender\2.66\scripts\startup\bl_ui\space_image.py", line 376, in draw
  if ima and ima.is_dirty:

AttributeError: 'ID' object has no attribute 'is_dirty'

location: :-1

%%%

%%%--- Operating System, Graphics card --- Windows 7 64bit, Geforce 560ti - Blender version with error, and version that worked --- Successfully repeated in 2.66.5 r55767 And was actually able to reproduce this in 2.49b... Wow. - Short description of error --- Assigning a texture to selected faces, then doing a certain pattern of mode switching and undoing will either break the UV/image editor or crash Blender. Screenshot of the error (with console errors visible too) is attached. - Steps for others to reproduce the error (preferably based on attached .blend file) --- 1. Open attached .blend file 2. Enter edit mode 3. Make sure all faces are selected 4. Assign a new image to the mesh (click New in the image editor) 5. Enter object mode 6. Undo (So the texture disappears from the image editor view) 7. Enter edit mode 8. Undo The image editor should now look like it does in the attached screenshot. This has not been 100% repeatable, but it happens more often than not. If nothing happens after step 8, repeat from step 5. Sometimes Blender will even crash completely (quick exit, no error or crash dialog given) when returning to object mode, even if the image editor doesn't visually break. Console outputs this error (among others): Traceback (most recent call last): ``` File "C:\Program Files\Blender Foundation\Blender\2.66\scripts\startup\bl_ui\space_image.py", line 376, in draw if ima and ima.is_dirty: ``` AttributeError: 'ID' object has no attribute 'is_dirty' location: <unknown location>:-1 %%%

Bjørnar Frøyse commented

2013-04-04 15:00:15 +02:00

Changed status to: 'Open'

Ton Roosendaal commented

2013-04-05 12:13:28 +02:00

%%%How did you save this file? It's including the userpreferences, that's quite not standard....
On loading the file it also complains about a missing fbx add-on. Just do tests on 'factory settings' to be sure?

I only could do a crash once, right after adding the image:
http://www.pasteall.org/41086

Redoing your cycle of instructions didn't crash ever.

%%%

%%%How did you save this file? It's including the userpreferences, that's quite not standard.... On loading the file it also complains about a missing fbx add-on. Just do tests on 'factory settings' to be sure? I only could do a crash once, right after adding the image: http://www.pasteall.org/41086 Redoing your cycle of instructions didn't crash ever. %%%

Bjørnar Frøyse commented

2013-04-05 12:47:05 +02:00

%%%Here's a video recorded after renaming the 2.66 folder in %appdata%\Blender Foundation\Blender. That should count as a factory reset, right?

http://www.youtube.com/watch?v=cqX8imiQyxs

I could also reproduce this behaviour on two other computers here. (As well as in 2.49b, which surprised me)

Here's a console screenshot with --debug active: http://www.pasteall.org/pic/show.php?id=48636

Should be noted that I usually can't get it to crash from this, but it does happen.%%%

%%%Here's a video recorded after renaming the 2.66 folder in %appdata%\Blender Foundation\Blender\. That should count as a factory reset, right? http://www.youtube.com/watch?v=cqX8imiQyxs I could also reproduce this behaviour on two other computers here. (As well as in 2.49b, which surprised me) Here's a console screenshot with --debug active: http://www.pasteall.org/pic/show.php?id=48636 Should be noted that I usually can't get it to *crash* from this, but it does happen.%%%

Bjørnar Frøyse commented

2013-04-05 13:06:47 +02:00

%%%Regarding how I saved the file, it was probably a renamed copy of a near-factory startup.blend. In hindsight probably a bad way of doing it, but I wanted to be sure that whoever opened the file would see exactly the same as me.%%%

Sergey Sharybin commented

2013-04-05 13:12:29 +02:00

%%%Ton, found a typo in code which likely caused your crash.

As for this issue -- i could not reproduce it. IT could be caused by some addon or so. Is it possible to reproduce the issue after loading factory settings?%%%

%%%Ton, found a typo in code which likely caused your crash. As for this issue -- i could not reproduce it. IT could be caused by some addon or so. Is it possible to reproduce the issue after loading factory settings?%%%

Bjørnar Frøyse commented

2013-04-05 14:43:53 +02:00

%%%I could reproduce it after loading factory settings, exactly as described in the report here. Will test it on two other computers tomorrow.

Here's my system info, if it helps. Prior to printing this, Blender Foundation folder in %Appdata% was deleted, and Blender was extracted to a new folder, to avoid all residue of old stuff and/or addons.

http://www.pasteall.org/41089/text%%%

%%%I could reproduce it after loading factory settings, exactly as described in the report here. Will test it on two other computers tomorrow. Here's my system info, if it helps. Prior to printing this, Blender Foundation folder in %Appdata% was deleted, and Blender was extracted to a new folder, to avoid all residue of old stuff and/or addons. http://www.pasteall.org/41089/text%%%

Ton Roosendaal commented

2013-04-05 19:10:43 +02:00

%%%I found the issue, fix goes to svn.

It will give a usablity regression though - the undo stack for editmode now will get freed if you are undo-ing outside editmode.%%%

%%%I found the issue, fix goes to svn. It will give a usablity regression though - the undo stack for editmode now will get freed if you are undo-ing outside editmode.%%%

Ton Roosendaal commented

2013-04-05 19:10:43 +02:00

Changed status from 'Open' to: 'Resolved'

Ton Roosendaal closed this issue

2013-04-05 19:10:43 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

UV/Image Editor breaks on mode change + undo #34866