Re: FF 3.5 and JS_GC Crashes

On Jul 23, 4:20 pm, Blake Kaplan <[email protected]> wrote:
> Are you dealing with JavaScript values in your C++? If so, then you might be
> running into what we call garbage collection hazards: the JS garbage collector
> doesn't know about references to JS objects from the C++ stack or heap, so
> unless you explicitly tell it about your references, it will collect objects
> that you're holding (see
> <https://developer.mozilla.org/en/SpiderMonkey_Garbage_Collection_Tips> for
> more information about this).

The C++ XPCOM component simply exposes a service which can return the
current (instantaneous) CPU for a given Win32 process. As such, I
don't believe there could be any JavaScript objects involved, right?
The IDL for the component is:

interface ICpuMonitor : nsISupports
{
  long GetPercentageCpuTime();
  attribute boolean enableMonitoring;
};

> It's also possible that you're running into bugs in either the engine (which
> is susceptable to the same sorts of problem) or in the implementation of
> jsdIDebuggerService... It's hard to tell exactly what's going on from here,
> though.
>
> There are a few debugging tricks you can use to track down these sorts of
> problems, but they require a debug build.

I see. I haven't used a debug build before. Do you archive a debug
build of the 3.5 GA release? If so, let me know where it is located
and the "debugging tricks" and I'll try to track down these crashes.

Thanks,
Glenn