[Gtk-sharp-list] Exception on closing a window.

libin libin.mohanan at wipro.com
Tue Jun 23 04:18:56 EDT 2009


 Any update on this guys??..

Am stuck with this :(

-----Original Message-----
From: libin [mailto:libin.mohanan at wipro.com] 
Sent: Friday, June 19, 2009 12:24 PM
To: 'Christian Hoff'
Cc: 'gtk-sharp-list at lists.ximian.com'
Subject: RE: [Gtk-sharp-list] Exception on closing a window.

 
I got cause of this problem.
Inside the child window (Which I am closing using 'x' button causing the
exception)code I am using 5 events of that window.

 		1.WindowStateEvent 
           	2.ConfigureEvent 
            3.FocusInEvent
           	4.ResizeChecked 
 		5.DeleteEvent 

And in configure event I am using with [GLib.ConnectBefore] attribute for
calling that event ahead of all.

When I am commenting the focusin event and resizechecked event the code is
running fine.

Is there any problem in using both of this events? Or whether there is any
problem in using these two events in conjunction with the configure event
with Glib.ConnectBefore?

Please throw some light on this.

Many Thanks,

Libin



-----Original Message-----
From: Christian Hoff [mailto:christian_hoff at gmx.net]
Sent: Wednesday, June 17, 2009 5:07 PM
To: libin
Cc: gtk-sharp-list at lists.ximian.com
Subject: Re: [Gtk-sharp-list] Exception on closing a window.

libin wrote:
>
> *These are the warnings shown in the output console*
>
> **
>
>  
>
> *Now this exception seems the problem because the exception thrown 
> while crashing comes from  glib-sharp.dll*
>
> **
>
> **(Project.exe:3364): GLib-GObject-CRITICAL **: g_type_free_instance: 
> assertion `instance != NULL && instance->g_class != NULL' failed
>
> Exception while disposing a Project.ModuleWindow in Gtk#
>
> A first chance exception of type 'System.AccessViolationException' 
> occurred in glib-sharp.dll
>
> The program '[3364] Project.exe: Managed' has exited with code 0 (0x0).
>
I have no idea what is really going on here, but it seems like an object is
disposed by your code before Gtk# tries to do that.

Set the environment variable "GTK_SHARP_DEBUG" to some value before you run
your program from the console. You should get a stack trace of the
GLib-Critical then. Post the stack trace to the list or file a bug report
with a small test case.
>
>  
>
> *Application crashes with this message.*
>
> >
>
> > Message: "*Attempted to read or write protected memory. This is 
> > often
>
> > an indication that other memory is corrupt." *
>
> > **
>
> > Source: *glib-sharp*
>
> >
>
> > Stack Trace:
>
> >
>
> > * at GLib.Object.PerformQueuedUnrefs()
>
> > at GLib.Timeout.TimeoutProxy.Handler()
>
> > at Gtk.Application.gtk_main()
>
> > at Gtk.Application.Run()
>
> > at LmEdit.LmEdit.Main() in D:\Lm_Edit\src\common\LmEdit.cs:line 49*
>
> > **
>
> > Any help would be highly appreciated.
>
>
> ----------------------------------------------------------------------
> --
>
> _______________________________________________
> Gtk-sharp-list maillist  -  Gtk-sharp-list at lists.ximian.com 
> http://lists.ximian.com/mailman/listinfo/gtk-sharp-list
>   




Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. 

www.wipro.com


More information about the Gtk-sharp-list mailing list