Log In
New Account
Home My Page Projects Blender 2.x BF release
Summary Activity Tracker SCM Files

Blender 2.6 Bug Tracker: Browse

[#26502] segmentationfault on pressing button to browse existing images for UV window

Date:
2011-03-14 20:38
Priority:
3
State:
Closed
Submitted by:
Bart Deruyter (bartje)
Assigned to:
Campbell Barton (campbellbarton)
Category:
Image & Movie I/O
Status:
Fixed / Closed
Relates to:
Duplicates:
Patches:
 
Summary:
segmentationfault on pressing button to browse existing images for UV window
Detailed description
Every time I press the button to browse through the already used images to load in the UV/image window, for UV-mapping, Blender crashes with a segmentation fault.

I've read somewhere this issue already had been fixed, but it appears to be back (just tried on a svn version of today... 14/03/2011).

Followup

Message
  • Date: 2011-03-14 22:11
  • Sender: Campbell Barton
  • cant redo this bug. Linux 2.6.37, 64bit. blender r35543
  • Date: 2011-03-14 22:44
  • Sender: Bart Deruyter
  • I am running linux 2.632-29-preempt, 64bit.

    After some testing it further, it also happens in trying to browse through the already used images for selecting them as texture.
  • Date: 2011-03-15 00:22
  • Sender: Sebastien Loss
  • Indeed bart.
    It happens to me too with 2.56 beta / Ubuntu lucid 64.
  • Date: 2011-03-15 00:59
  • Sender: Campbell Barton
  • fairly sure this isnt caused by long paths, > 240 chars which blender has trouble with, so Im not sure what to do.

    Would one of you be able to run this with gdb and get a backtrace?

  • Date: 2011-03-15 12:47
  • Sender: Ton Roosendaal
  • I think you have to more explicit. Which button precisely? The menu botton with tooltip "Browse Image to be linked" ?
    Does it crash before opening the menu, while using the menu, or after choosing an image?

    Second: this will most likely depend on the context you work on, like editmode or selections of faces you have. You need to help us by pin-pointing this case to something you can save in a .blend, which then causes a crash within 1 or 2 steps. Include the images you try to browse too. (max attachment size is 7 MB here)
  • Date: 2011-03-15 13:45
  • Sender: Bart Deruyter
  • Hi,

    I've done some more tests, and apparently it happens on this object.
  • Date: 2011-03-15 13:53
  • Sender: Bart Deruyter
  • Wow, sorry, my post wasn't complete. I've done more tests, and apparently the crashing happens in this file only. It both happens in edit and in object mode. I've attached a screenshot that shows which button I used, this time in the texture properties, but it also happens in the UV-window with the same button. I must say I started on the project in blender 2.49, and continued in the 2.5 series. Perhaps the file got corrupted somehow?

    I hope this helps.
  • Date: 2011-03-15 15:05
  • Sender: Bart Deruyter
  • I managed to run it with gdb, and had this as a result :

    Starting program: /home/bart/Documenten/Software/3D/install/linux2/blender
    [Thread debugging using libthread_db enabled]
    [New Thread 0x7fffe7f3c700 (LWP 11560)]
    found bundled python: /home/bart/Documenten/Software/3D/install/linux2/2.56/python
    read blend: /home/bart/Documenten/Animation/Het Vuur van Mondul/Kasteel.blend
    [New Thread 0x7fffdbfff700 (LWP 11568)]
    [New Thread 0x7fffdb7fe700 (LWP 11569)]
    [New Thread 0x7fffdaffd700 (LWP 11570)]
    [Thread 0x7fffdb7fe700 (LWP 11569) exited]
    [Thread 0x7fffdaffd700 (LWP 11570) exited]
    [New Thread 0x7fffdaffd700 (LWP 11571)]
    [New Thread 0x7fffdb7fe700 (LWP 11572)]
    [Thread 0x7fffdaffd700 (LWP 11571) exited]
    [Thread 0x7fffdb7fe700 (LWP 11572) exited]
    [Thread 0x7fffdbfff700 (LWP 11568) exited]
    [New Thread 0x7fffdbfff700 (LWP 11574)]
    [New Thread 0x7fffdb7fe700 (LWP 11575)]
    [New Thread 0x7fffdaffd700 (LWP 11576)]
    [Thread 0x7fffdb7fe700 (LWP 11575) exited]
    [New Thread 0x7fffdb7fe700 (LWP 11577)]
    [Thread 0x7fffdaffd700 (LWP 11576) exited]
    [New Thread 0x7fffdaffd700 (LWP 11578)]
    [Thread 0x7fffdb7fe700 (LWP 11577) exited]
    [New Thread 0x7fffdb7fe700 (LWP 11579)]
    [Thread 0x7fffdaffd700 (LWP 11578) exited]
    [New Thread 0x7fffdaffd700 (LWP 11580)]
    [Thread 0x7fffdb7fe700 (LWP 11579) exited]
    [New Thread 0x7fffdb7fe700 (LWP 11581)]
    [Thread 0x7fffdaffd700 (LWP 11580) exited]
    [New Thread 0x7fffdaffd700 (LWP 11582)]
    [Thread 0x7fffdb7fe700 (LWP 11581) exited]
    [Thread 0x7fffdaffd700 (LWP 11582) exited]
    [Thread 0x7fffdbfff700 (LWP 11574) exited]
    [New Thread 0x7fffdbfff700 (LWP 11591)]
    [New Thread 0x7fffdaffd700 (LWP 11592)]
    [New Thread 0x7fffdb7fe700 (LWP 11593)]
    [Thread 0x7fffdaffd700 (LWP 11592) exited]
    [Thread 0x7fffdb7fe700 (LWP 11593) exited]
    [New Thread 0x7fffdb7fe700 (LWP 11594)]
    [New Thread 0x7fffdaffd700 (LWP 11595)]
    [Thread 0x7fffdaffd700 (LWP 11595) exited]
    [New Thread 0x7fffdaffd700 (LWP 11596)]
    [Thread 0x7fffdaffd700 (LWP 11596) exited]
    [Thread 0x7fffdb7fe700 (LWP 11594) exited]
    [New Thread 0x7fffdb7fe700 (LWP 11597)]
    [New Thread 0x7fffdaffd700 (LWP 11598)]
    [Thread 0x7fffdb7fe700 (LWP 11597) exited]
    [Thread 0x7fffdaffd700 (LWP 11598) exited]
    [New Thread 0x7fffdb7fe700 (LWP 11599)]
    [Thread 0x7fffdb7fe700 (LWP 11599) exited]
    [Thread 0x7fffdbfff700 (LWP 11591) exited]
    [New Thread 0x7fffdbfff700 (LWP 11601)]

    Program received signal SIGSEGV, Segmentation fault.
    [Switching to Thread 0x7fffdbfff700 (LWP 11601)]
    0x0000000000c0e53a in IMB_scalefastImBuf ()

    I hope this helps too.

    grtz,
    Bart
  • Date: 2011-03-15 15:28
  • Sender: Campbell Barton
  • Likely this is an error scaling down an image for a thumbnail, can you check to see if its a specific directory's files which causes this crash?
  • Date: 2011-03-15 15:47
  • Sender: Bart Deruyter
  • I've reproduced the crash with a new file, using the same image as texture by first loading the image as the texture, then clicking on the button I've shown on the image that I've attached. So I guess you're right.
  • Date: 2011-03-15 22:12
  • Sender: Campbell Barton
  • Can you try narrow down which image is causing this segfault?
    you could do this to temporarily moving images out of the dir until the crash doesnt happen, to work out the offending image.

    you could also try run blender with strace to see which image is opened before the crash
    strace -e trace=open blender

  • Date: 2011-03-17 05:30
  • Sender: Alexander Kuznetsov
  • Campbell Barton, the Blender crashes if one side (width) of a texture > 32768
    When you click on list icon, Blender crashes.Dunno if it is the same bug.
  • Date: 2011-03-17 05:35
  • Sender: Alexander Kuznetsov
  • Bart Deruyter, can you attach the problematic image texture?
  • Date: 2011-03-17 06:50
  • Sender: Campbell Barton
  • should have tried making a jpeg this big and viewing thumbnail.
    confirmed the crash, looking into this.
  • Date: 2011-03-17 12:09
  • Sender: Campbell Barton
  • this bug has been in blender since going opensource, good find!
    fixed r35594.
 

Attached Files:

Name Date Download
blendercrashing icon.jpg 2011-03-15 13:45 Download

Changes:

Field Old Value Date By
status_idOpen2011-03-17 12:09campbellbarton
close_dateNone2011-03-17 12:09campbellbarton
StatusReady2011-03-17 12:09campbellbarton
assigned_tonone2011-03-17 06:50campbellbarton
StatusNew2011-03-17 06:50campbellbarton
File Added15412: blendercrashing icon.jpg2011-03-15 13:45bartje