Page MenuHome

File Browser Access Crashes Blender - TIFF Interface Layer - DDS - libpng error - Sef Fault
Closed, ArchivedPublic

Description

Accessing file manager crashes blender, for a few days now.

Linux 64bit Karmic Koala

v27667

console says:

TIFFReadDirectory: Warning, (Blender TIFF Interface Layer): invalid TIFF directory; tags are not sorted in ascending order.
TIFFReadDirectory: Warning, (Blender TIFF Interface Layer): unknown field with tag 11 (0xb) encountered.
MissingRequired: (Blender TIFF Interface Layer): TIFF directory is missing required "ImageLength" field.
imb_loadtiff: could not open TIFF IO layer.
DDS: trying to read beyond end of stream (corrupt file?)DDS: trying to read beyond end of stream (corrupt file?)DDS: trying to read beyond end of stream (corrupt file?)DDS: trying to read beyond end of stream (corrupt file?)DDS: trying to read beyond end of stream (corrupt file?)DDS: trying to read beyond end of stream (corrupt file?)DDS: trying to read beyond end of stream (corrupt file?)DDS: trying to read beyond end of stream (corrupt file?)DDS: trying to read beyond end of stream (corrupt file?)DDS: trying to read beyond end of stream (corrupt file?)DDS: trying to read beyond end of stream (corrupt file?)DDS: trying to read beyond end of stream (corrupt file?)DDS: trying to read beyond end of stream (corrupt file?)DDS: trying to read beyond end of stream (corrupt file?)DDS: trying to read beyond end of stream (corrupt file?)DDS: trying to read beyond end of stream (corrupt file?)DDS: trying to read beyond end of stream (corrupt file?)DDS: trying to read beyond end of stream (corrupt file?)DDS: trying to read beyond end of stream (corrupt file?)DDS: trying to read beyond end of stream (corrupt file?)DDS: trying to read beyond end of stream (corrupt file?)DDS: trying to read beyond end of stream (corrupt file?)DDS: not valid; header follows
Flags: 0x000B0001
DDSD_CAPS
DDSD_LINEARSIZE
DDSD_MIPMAPCOUNT
Height: 917506
Width: 1703936
Depth: 1632763904
Linear size: 0
Mipmap count: 1970566007
Pixel Format:
Flags: 0x00000000
FourCC: ''
Bit count: 0
Red mask: 0x00000000
Green mask: 0x00000000
Blue mask: 0x00000000
Alpha mask: 0x00000000
Caps:
Caps 1: 0x00001000
DDSCAPS_TEXTURE
Caps 2: 0x00000000
Caps 3: 0x00000000
Caps 4: 0x00000000
Version:
NVIDIA Texture Tools 0.9.5
Unknown fileformat
libpng error: Image width or height is zero in IHDR
Memoryblock free: pointer not in memlist
Segmentation fault

Event Timeline

oops typo 'seg fault'.

Hi, it's probably because of a particular file in that folder that's causing a problem when the file browser tries to make preview images. Can you please try and find the actual file in question so we can test it? One way to narrow it down quickly is:
* move all the files in that folder to another folder
* test to see if it crashes
* if it doesn't crash, move that group of files out and swap the other original half back in
* if it does crash, move half of the existing files out, and repeat

Ok, found the culprit :-) following your advice.

link to file:

http://www.onedrop.it/Luigi/ftp/MVI_0049.MOV

The file is from a Canon T2i EOS 550. It is mpeg4 AVC with 48khz 16bit PCM audio in a .mov container.

But I have other Canon 5DmkII, 7D and T2i mpeg4 AVC files in the same folder but they are 44khz 16bit PCM audio in a .mov container.

The 44khz audio files don't crash 2.5 browsing the folder, HOWEVER they do crash blender putting them in the VSE and scrubbing them. They don't crash blender if audio is disabled.

So weird as it sounds, 9pun not intended) I think it's the higher audio sample rate causing the crash.

I also think this is only Linux related, as there is a thread on BA where Windows Vista users are happily scrubbing the file in the link above as a test.

Cheers for the speedy reply.

Just a minor correction, using latest svn 27667, although the other Canon AVC video files (those with 44khz audio) don't crash blender whilst file browsing, they do cause a seg fault as soon as I attempt to 'Add' them to the VSE. That didn't happen before. :-(

Ok, last one. :-)

Testing a bit more regarding file browser crash. I've taken the file out of the default folder blender starts up with and don't get a crash browsing. i can then continue browsing into the folder containing the culprit file, without issue. So it seems like it only crashes blender via file browsing if the culprit file is in the initial folder that the file browser opens in.

They all then crash blender adding them to the VSE with:

Memoryblock free: pointer not in memlist
Segmentation fault

I've also tried setting sound to None in user preferences, SDl and Jack, crashes all the same.

Ok, I tried this out here on my osx machine, once with FFMPEG enabled and with Quicktime disabled, and vice versa. Both times worked fine without crashes, using Image->open to open the movie up in the image editor and scrub back and forth, though the time I had FFMPEG enabled, I got this in the console:

Memoryblock free: pointer not in memlist
Memoryblock MORE THAN 1 MEMORYBLOCK CORRUPT: error in header
Memoryblock MORE THAN 1 MEMORYBLOCK CORRUPT: error in header
(and lots more of these last ones).

So I suspect it's an FFMPEG issue, possibly related to whatever version you've got on linux there...

Matt

Ok, my problem with Ubuntu Karmic 64bit stable FFMPEG.

I've been trying to use a local FFMPEG build but Blender fails to build due to a scons error, I raised a bug report and hopefully Nathan will look at it when he can, been assigned.

Cheers and apologies.

Hi Matt

Again due to the 16 - 235 clamping patch I've moved FFMPEG from stable Ubuntu 64bit Karmic binaries to building it from svn at /usr and now no crashes.

Resolved as you suspected with a later FFMPEG build. :-)

Hi,

An FFMPEG bug and it's fixed in the last version, time to close the report :)

- Diego

Diego Borghetti (bdiego) changed the task status from Unknown Status to Archived.Jun 2 2010, 12:37 AM