Crash after disabling then enabling the Banshee.OpenVP extension about openvisualizationplatform

[GoogleCodeExporter]

Hmm... something tells me that Banshee or Gtk# should not be trying to use this
constructor at all.

Original comment by [email protected] on 30 Aug 2008 at 7:47

• Added labels: Patch

[GoogleCodeExporter]

I don't really understand it, but similar patches have fixed crashes in banshee.

See 
http://www.go-mono.com/docs/index.aspx?link=T%3AGLib.MissingIntPtrCtorException
for an explanation

Original comment by [email protected] on 30 Aug 2008 at 8:06

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Right, I know that's why it's upset but the only way it's going to call this
constructor is if the managed object is disposed and the native object is not
destroyed, which is an issue.  If the managed object is "revived" it will be 
with
null/default field values.  This widget will not work in that case, and I don't
expect that Banshee is even trying to use it again (since it would need a 
managed
reference anyway).

So it seems like Gtk# itself is resurrecting the native object in managed land 
for
some inexplicable reason.  I'd be interested to know what this reason is.  I 
suspect
it is a bug somewhere else, and adding this constructor will treat the symptom, 
but
not the cause.

Anyway, I'll probably be committing the patch anyway.  Thanks for submitting it.

Original comment by [email protected] on 30 Aug 2008 at 10:54

[GoogleCodeExporter]

Original comment by [email protected] on 17 Sep 2008 at 7:48

• Added labels: Product-OpenVP-Banshee

[GoogleCodeExporter]

I wasn't able to reproduce the crash anymore with the latest svn and the latest 
patch.

Original comment by [email protected] on 22 Jan 2009 at 8:04

[GoogleCodeExporter]

The latest version of mono-addins seems to resolve this issue.

Original comment by [email protected] on 22 Jan 2009 at 9:19

• Changed state: Fixed
• Removed labels: Patch