Shotwell segfaults in libmpeg
Submitted by an unknown user
Link to original bug (#718019)
Description
---- Reported by shotwell-maint@gnome.bugs 2011-08-27 12:01:00 -0700 ----
Original Redmine bug id: 4029
Original URL: http://redmine.yorba.org/issues/4029
Searchable id: yorba-bug-4029
Original author: Dominique Leuenberger
Original description:
Since recently, my shotwell crashes on startup after a few seconds, while scanning the library (~ 10000 objects at this moment).
The backtrace:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffcb7fb700 (LWP 27037)]
0x00007fffcbd8d6b1 in mpeg2_idct_copy_sse2 () from /usr/lib64/libmpeg2.so.0
(gdb) bt full
#0 0x00007fffcbd8d6b1 in mpeg2_idct_copy_sse2 () from
/usr/lib64/libmpeg2.so.0
No symbol table info available.
#1 0x00007fffcbd8763d in mpeg2_slice () from /usr/lib64/libmpeg2.so.0
No symbol table info available.
#2 0x00007fffcbd7d6f8 in mpeg2_parse () from /usr/lib64/libmpeg2.so.0
No symbol table info available.
#3 0x00007fffcbf9ba1e in ?? () from
/usr/lib64/gstreamer-0.10/libgstmpeg2dec.so
No symbol table info available.
#4 0x00007ffff74c1c1a in gst_pad_push (pad=0x4eab030, buffer=0x620c000) at
gstpad.c:4684
cache = 0xb38d90
ret =
cache_ptr = 0x4eab1a8
peer = 0x4eabab0
caps =
PRETTY_FUNCTION = "gst_pad_push"
#5 0x00007fffd25de991 in ?? () from
/usr/lib64/gstreamer-0.10/libgstmpegvideoparse.so
No symbol table info available.
#6 0x00007fffd25df5ca in ?? () from
/usr/lib64/gstreamer-0.10/libgstmpegvideoparse.so
No symbol table info available.
#7 0x00007ffff74c1c1a in gst_pad_push (pad=0x5c76630, buffer=0x6259100) at
gstpad.c:4684
cache = 0x4b35490
ret =
cache_ptr = 0x5c767a8
peer = 0x5c767b0
caps =
PRETTY_FUNCTION = "gst_pad_push"
#8 0x00007fffd1b0e6e0 in ?? () from
/usr/lib64/gstreamer-0.10/libgstcoreelements.so
No symbol table info available.
#9 0x00007ffff74e7e64 in gst_task_func (task=0x56d5260) at gsttask.c:318
lock = 0x4e9ac80
tself = 0x56da760
priv = 0x56d5300
PRETTY_FUNCTION = "gst_task_func"
#10 0x00007ffff43e1968 in ?? () from /usr/lib64/libglib-2.0.so.0
---Type <return> to continue, or q <return> to quit---
No symbol table info available.
#11 0x00007ffff43df446 in ?? () from /usr/lib64/libglib-2.0.so.0
No symbol table info available.
#12 0x00007ffff3cbeeb5 in start_thread () from /lib64/libpthread.so.0
No symbol table info available.
#13 0x00007ffff3a021ad in clone () from /lib64/libc.so.6
No symbol table info available.
Same happens in the just released version 0.11.0
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:45:00 -0700 ----
History
Comment 1
Updated by Lucas Beeler about 2 years ago
- Category set to 4
- Priority changed from Normal to Urgent
- Target version set to 0.12
@ Dominque:
Thanks for reporting this bug. I can tell you what's going on here. On startup, Shotwell attempts to extract duration and framesize information from any video files in your library that it hasn't been able to read previously (e.g., if you didn't have an appropriate CODEC installed before but now you do). In your case, unfortunately, one of your videos is causing the GStreamer library used by Shotwell to extract video information to crash. So I'm guessing this problem started happening when some new video file was added to your library. Did you import any video files around the time this problem started occuring? If you can figure out which video file is causing the crash, send it to us (if it's too big to attach here, upload it to a filesharing service like Dropbox and send us a link to it) so we can debug the problem further. One thing that might be helpful in figuring out what file is causing the problem is to look at the Shotwell logfile. To learn how to run Shotwell with logging turned on, see the "I found a bug in Shotwell. How can I report it?" section of the Shotwell FAQ here: http://redmine.yorba.org/projects/shotwell/wiki/ShotwellFAQ.
Comment 2
Updated by Lucas Beeler about 2 years ago
Comment 3
Updated by Lucas Beeler about 2 years ago
Unless the original reporter can provide us with an MPG file or a log that sheds more light on the problem before Oct. 1, I'm going to mark this ticket worksforme.
Comment 4
Updated by Dominique Leuenberger about 2 years ago
Lucas Beeler wrote:
bq.
Unless the original reporter can provide us with an MPG file or a log that sheds more light on the problem before Oct. 1, I'm going to mark this ticket worksforme.
Sorry... just returned from a 3 week vacation and honey moon :P Had completely different thins on mind than this.
I could narrow it down to one of two videos already... will find which of the two must be the offender and try to provide it.
Thanks for your patiance!
Dominique
Comment 5
Updated by Dominique Leuenberger about 2 years ago
Actually found that one of the MPG files was imported as being 0 bytes, which caused the crash over and over... not sure why the import itself failed, but should be simple enough to reproduce (I doubt it's useful to attach a 0B file)
Comment 6
Updated by Jim Nelson about 2 years ago
I can't reproduce this. I created a zero-byte .mpg file in my Pictures directory. Shotwell detected and auto-imported it (which perhaps is not the best behavior; see #2947 (closed)). Are you sure this is what's causing the crash? You might try following these directions and attaching the resulting files to this ticket:
http://redmine.yorba.org/projects/shotwell/wiki/ShotwellFAQ#I-found-a-bug-in- Shotwell-How-can-I-report-it
Comment 7
Updated by Dominique Leuenberger about 2 years ago
Ok... I found another video which has the same effect. I'll gladly share this with you but would not like the video to be publically shared (personal vid).
OTOH I am now confident that this is not a shotwell bug but must be somewhere in an underlying library, as totem crashes the same way playing this video (whereas vlc plays it just fine... totem uses gstreamer as well)
Comment 8
Updated by Adam Dingle about 2 years ago
- Status changed from Open to 5
- Resolution set to invalid
Dominique, thanks for your debugging efforts. As you said, if Totem crashes playing this video then this is not a Shotwell bug, so I'm closing this ticket. You should probably report this bug to the GStreamer team.
Comment 9
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Invalid
--- Bug imported by chaz@yorba.org 2013-11-25 21:54 UTC ---
This bug was previously known as bug 4029 at http://redmine.yorba.org/show_bug.cgi?id=4029
Unknown Component Using default product and component set in Parameters Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Version: 0.12
Resolution: RESOLVED INVALID