rhythmbox-metadata crashed with SIGSEGV in jpeg_idct_ifast()

Bug #178724 reported by René Pärts
382
This bug affects 48 people
Affects Status Importance Assigned to Milestone
libjpeg6b (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: rhythmbox

happened in ubuntu hardy when i started rhythmbox and it started looking for new files in specified folders
rhythmbox compiled from latest svn

ProblemType: Crash
Architecture: i386
Date: Wed Dec 26 15:23:48 2007
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
NonfreeKernelModules: cdrom
Package: rhythmbox 0.11.4-0ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
ProcCwd: /home/hit
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=et_EE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 jpeg_idct_ifast () from /usr/lib/libjpeg.so.62
 ?? () from /usr/lib/libjpeg.so.62
 ?? ()
 ?? ()
 ?? ()
Title: rhythmbox-metadata crashed with SIGSEGV in jpeg_idct_ifast()
Uname: Linux hit 2.6.24-2-generic #1 SMP Thu Dec 20 17:36:12 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev oident plugdev powerdev sambashare scanner vboxusers video
SegvAnalysis:
 Segfault happened at: 0xb5a93491 <jpeg_idct_ifast+1937>: mov %al,(%ecx)
 PC (0xb5a93491) ok
 source "%al" ok
 destination "(%ecx)" (0x00000001) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA

Revision history for this message
René Pärts (renep) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:decompress_onepass (cinfo=0x8208cdc, output_buf=0xb62b2fc4) at ./jdcoefct.c:197
jpeg_read_raw_data (cinfo=0x8208cdc, data=0xb62b2fc4, max_lines=8)
gst_jpeg_dec_chain (pad=0x8101298, buf=0x80f2850) at gstjpegdec.c:701
?? () from /usr/lib/libgstreamer-0.10.so.0
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in libjpeg6b:
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Jonathan Thomas (echidnaman) wrote :
Download full text (33.0 KiB)

A copy of the best, most recent backtrace:

#0 0xb695e15e in jpeg_idct_ifast (cinfo=0xa0268c4, compptr=0xa136d08, coef_block=0xa13f80c, output_buf=0xb6985ff4,
    output_col=0) at ./jidctfst.c:347
 tmp0 = -390
 tmp1 = -70
 tmp2 = 1160
 tmp3 = 1184
 tmp4 = 33
 tmp5 = -45
 tmp6 = -1227
 tmp7 = -1511
 tmp10 = <value optimized out>
 tmp11 = 545
 tmp12 = <value optimized out>
 tmp13 = <value optimized out>
 z5 = <value optimized out>
 z10 = <value optimized out>
 z11 = <value optimized out>
 z12 = <value optimized out>
 z13 = -306
 inptr = (JCOEFPTR) 0xa13f81c
 quantptr = (IFAST_MULT_TYPE *) 0xa137674
 wsptr = (int *) 0xb69179b0
 outptr = (JSAMPROW) 0xdec0 <Address 0xdec0 out of bounds>
 range_limit = (
    JSAMPLE *) 0xa136efc "\200\201\202\203\204\205\206\207\210\211\212\213\214\215\216\217\220\221\222\223\224\225\226\227\230\231\232\233\234\235\236\237 ¡¢£¤¥¦§¨©ª«¬­®¯°±²³´µ¶·¸¹º»¼½¾¿ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþ", 'ÿ' <repeats 73 times>...
 ctr = 0
 workspace = {471, -1242, -889, -397, -74, 91, 102, 37, 2332, 231, 68, -84, -131, -233, -165, -43, 2396, 168,
  94, -1, -191, -185, -82, -35, 2376, 229, 7, -141, -225, -189, -128, -37, 2448, 225, 75, -189, -225, -227, -60, -19,
  2458, 348, -94, -221, -233, -143, -66, -9, 2478, 377, -8, -258, -261, -187, -55, -49, 2449, 280, 27, -221, -292,
  -175, -74, -13}
#1 0xb695c4c4 in decompress_data (cinfo=0xa0268c4, output_buf=0xb6947c60) at ./jdcoefct.c:362
 coef = (my_coef_ptr) 0xa137b94
 last_iMCU_row = 41
 block_num = 0
 ci = 3
 block_rows = 1
 buffer = (JBLOCKARRAY) 0xa137e0c
 buffer_ptr = (JBLOCKROW) 0xa13f88c
 output_ptr = (JSAMPARRAY) 0xb6985ff4
 output_col = 0
 compptr = (jpeg_component_info *) 0xa136d08
 inverse_DCT = (inverse_DCT_method_ptr) 0xb695dd00 <jpeg_idct_ifast>
#2 0xb6955b4f in jpeg_read_raw_data (cinfo=0xa0268c4, data=0xb6947c60, max_lines=8) at ./jdapistd.c:210
 lines_per_iMCU_row = 8
#3 0xb697c97a in gst_jpeg_dec_decode_indirect (dec=<value optimized out>, base=0xb6947f64, last=0xb6947f58,
    width=428, height=334, r_v=1, r_h=1) at gstjpegdec.c:706
 y = {
  "\004\023VOSWUVVTXXVXXVZVUZ\026\004\002\005\004\005\003\001\004\004\003\003\006\003\001\004\002\005\004\005\004\004\002\006\001\005\005\003\003\001\005\004\003\004\004\003\003\003\003\004\004\004\004\004\004\005\004\003\003\003\003\003\002\004\003\003\005\004\002\003\004\003\003\004\004\003\004\005\004\003\003\004\004\003\003\004\004\003\005\003\003\004\004\005\002\005\005\003\004\004\003\004\003\003\003\004\004\004\004\004\004\003\003\004\005\003\003\004\003\003\003\003\004\004\004\004\005\002\003\003\004\005\003\004\003\003\003\003\004\005\004\003\003\004\003\003\004\003\003\005\004\003\002\004\003\002\005\004\004\004\004\003\003\004\004\004\004\004\004\004\004\003\002\004\004\004\003\003\003\003\004\003\004\004\003\003\004\004\004\003"...,
  "\0030¤¬¬®¯³­­°®¬®¯°¬©´ªJ-1+(++*++**&,--)*()(**/,-+*-)++)**,/-++*)*+**+*+,,,)*))+++,(((*+****))*+++,**,+**'(*,+()**,*++*))**-+*)))*,**+,,+++*)+++,*,+**+,++*++**,+*+*((()))*(()**))())))+**,))(*+,+***+*)*+,"...,
  "\004+§©§«­ª¬­¯¬ª««¯®®ª²©¬¬­­­ª§§©ª¬¬¬¦§ª­¨¨§¨§©©«ª¬ª¥©««ª©«®¬ª¨§¦§¨«««ª©ª©¨¥¦¥¥§¨§¨¤£...

Changed in libjpeg6b (Ubuntu):
importance: Low → Medium
Kees Cook (kees)
description: updated
Revision history for this message
datakid (datakid) wrote :

my bug is the same, although in fully up to date Karmic.

Revision history for this message
p3tris (p3tris) wrote :

me too. Same bug after upgrading to Karmic.

Revision history for this message
dino99 (9d9) wrote :

That version has died long ago; no more supported

Changed in libjpeg6b (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.