Can you get a stack trace of where it dies?

Unhandled Exception: System.NullReferenceException: Object reference not set to
an instance of an object
in (wrapper unknown) Gdk.Rectangle:PtrToStructure (intptr,object)
in <0x00000> <unknown method>
in (wrapper managed-to-native)
System.Runtime.InteropServices.Marshal:PtrToStructure (intptr,System.Type)in
<0x000c1> Gdk.Region:GetRectangles ()
in <0x00055> IconView:OnExposeEvent (Gdk.EventExpose args)
in <0x0006f> Gtk.Widget:exposeevent_cb (IntPtr widget, IntPtr evnt)
in (wrapper native-to-managed) Gtk.Widget:exposeevent_cb (intptr,intptr)
in <0x00000> <unknown method>
in (wrapper managed-to-native) Gtk.Application:gtk_main ()
in <0x00008> Gtk.Application:Run ()
in <0x00010> Gnome.Program:Run ()
in <0x0057c> Driver:Main (System.String[] args)

is this still an issue in 0.1.5?

*** Bug 326468 has been marked as a duplicate of this bug. ***

sfabel, can you try using cvs so we can see if this issue still persists and another stack trace could be nice? i have an ebuild you can overlay if you wish http://jonas.bergler.name/stuff/f-spot-999.ebuild

Still crashes.

Stack trace #1 (program crashed immediately after starting):
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 <0xb> (wrapper managed-to-native) System.Runtime.InteropServices.Marshal:PtrT oStringAnsi (intptr)
in <0xfffffffffffff8a5> (wrapper managed-to-native) System.Runtime.InteropServic es.Marshal:PtrToStringAnsi (intptr)
in [0x91] Mono.Data.SqliteClient.SqliteDataReader:ReadpVm (intptr,int)
in [0x46] Mono.Data.SqliteClient.SqliteDataReader:.ctor (Mono.Data.SqliteClient. SqliteCommand,intptr,int)
in <0xffffffffffffa405> (wrapper remoting-invoke-with-check) Mono.Data.SqliteCli ent.SqliteDataReader:.ctor (Mono.Data.SqliteClient.SqliteCommand,intptr,int)
in [0x68] Mono.Data.SqliteClient.SqliteCommand:ExecuteReader (System.Data.Comman dBehavior,bool,int&)
in [0x5] Mono.Data.SqliteClient.SqliteCommand:ExecuteReader (System.Data.Command Behavior)
in [0x2] Mono.Data.SqliteClient.SqliteCommand:ExecuteReader ()
in <0xcf> TagStore:LoadAllTags ()
in <0x8d> TagStore:.ctor (Mono.Data.SqliteClient.SqliteConnection,bool)
in <0xf8> Db:.ctor (string,bool)
in <0x280> Driver:Main (string[])
in <0xffffffffc047826e> (wrapper runtime-invoke) System.Object:runtime_invoke_vo id_string[] (object,intptr,intptr,intptr)

Native stacktrace:

        mono(mono_handle_native_sigsegv+0x88) [0x504ad8]
        mono [0x4f180c]
        /lib/tls/libpthread.so.0 [0x2aaaab18c270]
        /lib/tls/libc.so.6(strlen+0x30) [0x2aaaab593260]
        mono(mono_string_new+0x2d) [0x48fc1d]
        [0x40252a43]

trace #2 (3rd time it started, this happened when scrolling down):
Starting new FSpot server

(..)

Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object
in (wrapper unknown) Gdk.Rectangle:PtrToStructure (intptr,object)
in <0x00000> <unknown method>
in (wrapper managed-to-native) System.Runtime.InteropServices.Marshal:PtrToStructure (intptr,System.Type)
in <0x000d4> Gdk.Region:GetRectangles ()
in <0x00044> IconView:PreloadRegion (Gdk.Region region, Int32 step)
in <0x00601> IconView:Scroll ()
in <0x0001a> IconView:HandleAdjustmentValueChanged (System.Object sender, System.EventArgs args)
in (wrapper delegate-invoke) System.MulticastDelegate:invoke_void_object_EventArgs (object,System.EventArgs)
in <0x000c9> GLib.Signal:voidObjectCallback (IntPtr handle, IntPtr gch)
in (wrapper native-to-managed) GLib.Signal:voidObjectCallback (intptr,intptr)
in <0x00000> <unknown method>
in (wrapper managed-to-native) Gtk.Application:gtk_main ()
in <0x00008> Gtk.Application:Run ()
in <0x0000c> Gnome.Program:Run ()
in <0x00514> Driver:Main (System.String[] args)

is this a 64bit machine?

My Machine is 64bit.(Dual Opteron)

uname -a
Linux gemini 2.6.14-gentoo-r5 #1 SMP PREEMPT Thu Jan 12 11:06:12 CET 2006 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ AuthenticAMD GNU/Linux

*** Bug 330095 has been marked as a duplicate of this bug. ***

Perhaps http://patches.ximian.com/Debugging could help to give some extra information on the stack traces?

Also crashes (freezes) on my 32bit HyperThreading (SMP Kernel) machine. Default SMP Kernel and libexif from Ubuntu Hoary and Dapper.

Sorry, can't give any debug information, because mono --trace outputs about 20mb per second...

Ok I tracked this down to a bug in gtk-sharp.  See http://bugzilla.ximian.com/show_bug.cgi?id=77658

I applied the patch to Gdk.Region, it's still freezing after some time with HyperThreading turned on.
Xlib: unexpected async reply (sequence 0x74ff1)!

Still here as well. Just got this when exporting to Original. Am also seeing the "unexpected async reply"...

=================================================================
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 <0x4> (wrapper managed-to-native) Exif.ExifData:exif_data_save_data (System.Runtime.InteropServices.HandleRef,intptr&,uint&)
in <0x81f11> (wrapper managed-to-native) Exif.ExifData:exif_data_save_data (System.Runtime.InteropServices.HandleRef,intptr&,uint&)
in <0x39> Exif.ExifData:Save ()
in <0x101> PixbufUtils:SaveJpeg (Gdk.Pixbuf,string,int,Exif.ExifData)
in <0x27f> FSpot.FolderGallery:ProcessImage (int)
in <0x26> FSpot.FolderGallery:Generate ()
in <0xe> FSpot.OriginalGallery:Generate ()
in <0x259> FSpot.FolderExport:Upload ()
in <0x2f0f48> (wrapper delegate-invoke) System.MulticastDelegate:invoke_void ()
in <0x21aec4f> (wrapper runtime-invoke) System.Object:runtime_invoke_void (object,intptr,intptr,intptr)

Native stacktrace:

        /usr/lib/libmono.so.0(mono_handle_native_sigsegv+0xdf) [0x77e21060]
        /usr/lib/libmono.so.0 [0x77de2ece]
        [0xffffe440]
        /usr/lib/libexif.so.12(exif_data_save_data+0x102) [0x755c8eb4]
        [0x75651060]
        [0x756d2f12]
        [0x756d1672]
        [0x756d0828]
        [0x756d04df]
        [0x756d040f]
        [0x756cf702]
        [0x75960768]
        [0x75c51681]
        /usr/lib/libmono.so.0 [0x77e002a8]
        /usr/lib/libmono.so.0(mono_runtime_invoke+0x33) [0x77e622ad]
        /usr/lib/libmono.so.0(mono_runtime_delegate_invoke+0x42) [0x77e6348b]
        /usr/lib/libmono.so.0 [0x77e93347]
        /usr/lib/libmono.so.0 [0x77edce2b]
        /usr/lib/libmono.so.0(GC_start_routine+0x5f) [0x77ef66dd]
        /lib/tls/i686/cmov/libpthread.so.0 [0x77cf9341]
        /lib/tls/i686/cmov/libc.so.6(__clone+0x5e) [0x77c6452e]

Created attachment 60370 [details] [review]
the patch that fixes this

Stian, does your PixbufUtils.cs include this patch?

The async reply bug is separate from the region bug, nico what version are you testing?

I'm running Current CVS version, Mono 1.1.13.2, gtk-sharp 2.8.1, libexif 0.6.12 (from Ubuntu Dapper, Kernel 2.6.15-16).

Larry,

it does now :P Bug fixed. But I couldn't reproduce that problem with a non-smp kernel, but I guess I might have tried to little.

I now got

The program 'f-spot' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadName (named color or font does not exist)'.
  (Details: serial 195134 error_code 15 request_code 154 minor_code 30)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

But I guess that's totally unrelated to the smp-bug (because I made dozens of galleries before I saw it), so I'll shut up about it here.

Still seeing the async reply bug, though. I'm also on Ubuntu Dapper...

I've opened http://bugzilla.gnome.org/show_bug.cgi?id=333071 on the async reply bug. I'm closing this one to keep the issues separate.