[Gtk-sharp-list] Gtk# and .NET2.0 crashing all over the place

Cody Russell bratsche at gnome.org
Sun Mar 18 11:03:52 EDT 2007

I *think* that gtk# is specifically targeted at .NET 1.1 at this point
still, so I think using it with .NET 2.0 might still be a "at your own
risk" type of thing.  I have used it with VS2005 Professional, but in
one or two places the runtime would emit a StackImbalanceException in
some of my custom widgets' drawing code.  Using all stock widgets, I
don't think I ever received any.  I never tried using VS2005 Express,
but it seems like that should behave the same as Professional.

I mostly use gtk# right now on VS2003 Professional, where it runs just
fine.  But that's not .NET 2.0.

/ Cody

On Sun, 2007-03-18 at 19:04 +1100, Aaron Oxford wrote:
> Hi all,
> I've given this its own topic now. I've disabled all timers and other 
> threads in my application and my app still crashes in random places 
> in the GUI. I'm getting everything from errors about loading icons 
> the wrong way through to crashes in Application.Run(). I've found 
> several postings about it on this list, all with no reply.
> To restate the problem in its entirety: My .NET2.0 application is 
> crashing and complaining about corrupt memory all the time on my Win 
> 2k3 + VCS2005 Express + Gtk# 2.8.3 platform. The crashes only started 
> since using Gtk# and are present even when only the Gtk# GUI is 
> running. The corruption is severe enough to affect other applications 
> running on my machine.
> My question is: are the developers aware of these problems, and if so 
> can we expect some fixes any time soon? Is Gtk# going to be a viable 
> option for me in the future - should I continue investing the 
> hundreds of hours it is taking to rewrite my GUI?

More information about the Gtk-sharp-list mailing list