On Apr 17, 9:02 am, [EMAIL PROTECTED] wrote:
> Greetings, I've been using Gecko 1.8.1.13 embedded into our
> Windows .NET 2.0 application via the "official" mozctlx.dll ActiveX
> wrapper and it has worked like a charm. However, recently we've been
> trying to update to the newest version of Gecko (1.9 pre5) due to the
> great rendering speed improvements and I've run into trouble -
> the .NET application, embedding Gecko as its main window, seems to
> crash arbitrarily, and the reasons given are either corrupted memory
> ("Attempted to read or write protected memory" in
> NativeMethods.DispatchMessage) or various .NET rendering exceptions
> ("GDI+ not ready", "Overflow" when drawing with Pen and such).
>
> Now, all of this is unfortunately very hard to track back to the Gecko
> component as it manifests itself only on Windows XP (not Vista) and
> usually after few hours of (gecko rendering) work, but a simple
> exchange for an older one seems to render our application back to the
> rock-stable state (one computer is particularly good at crashing it -
> all it takes is displaying a Windows Common OpenFileDialog and
> clicking on a file...there is a 20% chance each click will crash it).
>
> Yes, I know that the 1.9 prerelease 5 is really a prerelease and not a
> stable version, not whining that it might be broken ;) I would just
> like to know if the official ActiveX wrapper "mozctlx.dll", which is
> still part of the XULRunner source and is compiled regularly, is
> actually being developed and tested or has been long since abandoned
> (I know it's a very shallow embed, but still, there seems to be
> trouble now that hasn't been before). If not, whether there are some
> alternatives for us to use with the 1.9 engine. And whether someone
> actually is using this prerelease activex and how well it's going.
> Our application inside is a very, very heavy javascript engine written
> with Qooxdoo...it might be taking its toll.
The AcvtiveX control is _always_ built, but _never_ tested. This was
true in 1.8.1.x as well as 1.9 releases.
I would encourage you to use a debug build of XULRunner, which you'd
need to build yourself. That way you could use Visual Studio to debug
the crash, when it happens. Instructions for building XULRunner can be
found on MDC:
http://developer.mozilla.org/en/docs/Build_Documentation
http://developer.mozilla.org/en/docs/VC8_Build_Instructions
Other:
http://justdevelopment.blogspot.com/2008/04/building-xulrunner-and-winembed-using.html
Feel free to go on Mozilla IRC (irc.mozilla.org) and ask questions on
#xulrunner
Mark Finkle
_______________________________________________
dev-embedding mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-embedding
