crash on colour adjustments

Bug #37412 reported by sam tygier
8
Affects Status Importance Assigned to Milestone
mono
Fix Released
Unknown
f-spot (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

f-spot crashes when adjusting colors or converting to black and white or sepia, on jpegs.

to reproduce.
open f-spot
import some jpegs
go to edit mode
click the convert to black and white
or click on colour adjust and move a slider.

this is on an up to date dapper, f-spot 0.1.11-0ubuntu1 on powerpc.

Revision history for this message
sam tygier (samtygier) wrote :
Download full text (4.5 KiB)

lots of output when run from terminal.

Starting new FSpot server

=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

Stacktrace:

in (wrapper managed-to-native) Cms.Profile:f_cmsCreateBCHSWabstractProfile (int, double,double,double,double,double,Cms.ColorCIExyY,Cms.ColorCIExyY,System.Runtim e.InteropServices.HandleRef[]) <0xffffffff>
in (wrapper managed-to-native) Cms.Profile:f_cmsCreateBCHSWabstractProfile (int, double,double,double,double,double,Cms.ColorCIExyY,Cms.ColorCIExyY,System.Runtim e.InteropServices.HandleRef[]) <0xec>
in Cms.Profile:CreateAbstract (int,double,double,double,double,double,Cms.GammaT able[],Cms.ColorCIExyY,Cms.ColorCIExyY) <0x238>
in FSpot.Desaturate:GenerateProfile () <0x100>
in FSpot.ColorAdjustment:Adjust () <0x190>
in PhotoView:HandleDesaturateButtonClicked (object,System.EventArgs) <0xf4>
in (wrapper delegate-invoke) System.MulticastDelegate:invoke_void_object_EventAr gs (object,System.EventArgs) <0x8c>
in GLib.Signal:voidObjectCallback (intptr,intptr) <0x108>
in (wrapper native-to-managed) GLib.Signal:voidObjectCallback (intptr,intptr) <0 x38>
in (wrapper managed-to-native) Gtk.Application:gtk_main () <0xffffffff>
in (wrapper managed-to-native) Gtk.Application:gtk_main () <0x80>
in Gtk.Application:Run () <0xc>
in Gnome.Program:Run () <0x10>
in FSpot.Driver:Main (string[]) <0x6c8>
in (wrapper runtime-invoke) System.Object:runtime_invoke_void_string[] (object,i ntptr,intptr,intptr) <0x64>

Native stacktrace:

        /usr/lib/libmono.so.0(mono_handle_native_sigsegv+0x94) [0xfe74918]
        /usr/lib/libmono.so.0 [0xfe36724]
        [0x100380]
        [0x7fca3480]
        [0x3274505c]
        [0x32744ae4]
        [0x327446ac]
        [0x32742e04]
        [0x327428c8]
        [0x31fc5aa8]
        [0x325a51c4]
        [0x3215480c]
        /usr/lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__VOID+0x70) [0xeb7d c54]
        /usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x16c) [0xeb6d720]
        /usr/lib/libgobject-2.0.so.0 [0xeb8214c]
        /usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x6f4) [0xeb832b8]
        /usr/lib/libgobject-2.0.so.0(g_signal_emit+0x6c) [0xeb836fc]
        /usr/lib/libgtk-x11-2.0.so.0(gtk_button_clicked+0x7c) [0xf2a4fe0]
        /usr/lib/libgtk-x11-2.0.so.0 [0xf2a7404]
        /usr/lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__VOID+0x70) [0xeb7d c54]
        /usr/lib/libgobject-2.0.so.0 [0xeb6ce3c]
        /usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x16c) [0xeb6d720]
        /usr/lib/libgobject-2.0.so.0 [0xeb818ec]
        /usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x6f4) [0xeb832b8]
        /usr/lib/libgobject-2.0.so.0(g_signal_emit+0x6c) [0xeb836fc]
        /usr/lib/libgtk-x11-2.0.so.0(gtk_button_released+0x7c) [0xf2a4f10]
        /usr/lib/libgtk-x11-2.0.so.0 [0xf2a6444]
        /usr/lib/libgtk-x11-2.0.so.0(_gtk_marshal_BOOLEAN__BOXED+0x88) [0xf396bd c]
        /usr/lib/libgobjec...

Read more...

Revision history for this message
sam tygier (samtygier) wrote :

upstream traces this to a mono JIT bug http://bugzilla.ximian.com/show_bug.cgi?id=77968

Revision history for this message
Dean Loros (autocrosser) wrote :

Almost the same output with my system---Dual 1.25MDD--"normal" Dapper drake install from clean Breezy update.

sam tygier (samtygier)
Changed in f-spot:
status: Unconfirmed → Confirmed
Revision history for this message
sam tygier (samtygier) wrote :
Download full text (5.1 KiB)

this is still present in edgy as of 20060929.

Can i recommend that the the priority be increased, as this is a crasher in a default application when using a very user visible feature.

lcms: Error #12288; Corrupted memory profile
System.Exception: Invalid Profile Data
  at Cms.Profile..ctor (System.Byte[] data, Int32 start_offset, Int32 length) [0x00000]
  at JpegHeader.GetProfile () [0x00000]
open uri = file:///home/sam/Photos/2004/3/5/img_0024.jpg

=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

Stacktrace:

  at (wrapper managed-to-native) Cms.Profile.f_cmsCreateBCHSWabstractProfile (int,double,double,double,double,double,Cms.ColorCIExyY,Cms.ColorCIExyY,System.Runtime.InteropServices.HandleRef[]) <0xffffffff>
  at (wrapper managed-to-native) Cms.Profile.f_cmsCreateBCHSWabstractProfile (int,double,double,double,double,double,Cms.ColorCIExyY,Cms.ColorCIExyY,System.Runtime.InteropServices.HandleRef[]) <0x000ec>
  at Cms.Profile.CreateAbstract (int,double,double,double,double,double,Cms.GammaTable[],Cms.ColorCIExyY,Cms.ColorCIExyY) <0x00238>
  at FSpot.ColorDialog.AdjustmentProfile () <0x004e8>
  at FSpot.ColorDialog.Adjust () <0x00190>
  at FSpot.ColorDialog.RangeChanged (object,System.EventArgs) <0x00058>
  at (wrapper delegate-invoke) System.MulticastDelegate.invoke_void_object_EventArgs (object,System.EventArgs) <0x0008c>
  at GLib.Signal.voidObjectCallback (intptr,intptr) <0x00108>
  at (wrapper native-to-managed) GLib.Signal.voidObjectCallback (intptr,intptr) <0x00044>
  at (wrapper managed-to-native) Gtk.Application.gtk_main () <0xffffffff>
  at (wrapper managed-to-native) Gtk.Application.gtk_main () <0x00080>
  at Gtk.Application.Run () <0x0000c>
  at Gnome.Program.Run () <0x00010>
  at FSpot.Driver.Main (string[]) <0x007d4>
  at (wrapper runtime-invoke) System.Object.runtime_invoke_void_string[] (object,intptr,intptr,intptr) <0x00064>

Native stacktrace:

        mono(mono_handle_native_sigsegv+0xec) [0x1012308c]
        mono [0x100eca20]
        [0x100380]
        [0x103da700]
        /usr/lib/f-spot/libfspot.so.0(f_cmsCreateBCHSWabstractProfile+0x8c) [0xe06e0c4]
        [0x3358204c]
        [0x33581bec]
        [0x33580e6c]
        [0x335bcde4]
        [0x335bcbbc]
        [0x31ff6a78]
        [0x33508244]
        [0x32dddbc0]
        /usr/lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__VOID+0x6c) [0xecea1f0]
        /usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x158) [0xecd941c]
        /usr/lib/libgobject-2.0.so.0 [0xecedd78]
        /usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x888) [0xeceed8c]
        /usr/lib/libgobject-2.0.so.0(g_signal_emit+0x68) [0xeceef58]
        /usr/lib/libgtk-x11-2.0.so.0 [0xf56f924]
        /usr/lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__VOID+0x6c) [0xecea1f0]
        /usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x158) [0xecd941c]
        /usr/lib/libgobject-2.0.so.0 [0xeceda84]
        /usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x888) [0x...

Read more...

Changed in mono:
status: Unknown → Confirmed
Revision history for this message
sam tygier (samtygier) wrote :

From upstream

  ------- Comment #5 from Larry Ewing 2006-12-01 23:30 UTC -------
  I took another look at where we are actually using this and worked around the
  issue. It should be fixed CVS and will be released in 0.3.1.

i expect this will make it into feisty. maybe then we can ask for a backport to edgy/dapper

Changed in f-spot:
status: Confirmed → Fix Committed
Revision history for this message
sam tygier (samtygier) wrote :

0.3.1 was released today. once this makes it into ubuntu i can test if it is fixed.

Revision history for this message
sam tygier (samtygier) wrote :

i can confirm this is fixed with 0.3.2 in feisty

thanks

Changed in f-spot:
status: Fix Committed → Fix Released
Changed in mono:
status: Confirmed → Fix Released
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.