FF 3.5 and JS_GC Crashes
Glenn Boysko <[email protected]> Thu, 23 Jul 2009 07:27:28 -0700 (PDT)
| Newsgroups | gmane.comp.mozilla.devel.jsdebugger |
|---|---|
| Organization | http://groups.google.com |
| Message-ID | <[email protected]> |
Hello: I have written an extension that analyzes the performance of our company's multi-tier Web application. It inspects client-side behavior (it has a builtin JavaScript profiler and analyzes HTTP resource loading) as well as tracks backend delays (that contributes to end-to- end performance). The extension uses nsIWebProgressListener and jsdIDebuggerService APIs extensively. It also features a C++ XPCOM (to monitor browser process CPU usage) and an JavaScript XPCOM component. We are finding many crashes associated with Firefox 3.5 that we are not seeing with FF 3.0.x. The debug stacks seem to indicate failures in JS_GC and other JavaScript related APIs. Has anyone observed similar problems with the use of these APIs and FF 3.5? Does anyone have any suggestions for diagnosing the source of problems related to GC corruption? Or perhaps suggestions for coding that prevents these types of problems? Thanks, Glenn