Niky Williams wrote:
I ran the FireFox.exe it
produced and when I closed it, there were some "leaks" reported in the
text file. Is this normal for a FF build? Maybe some objects were
released on program close that the leak utility didn't account for?
Exactly. There are known bugs filed on
Niky Williams wrote:
Boris Zbarsky wrote:
The code looks ok to me. What does the output look like if you run
with memory leak logging (in a debug build; set XPCOM_MEM_LEAK_LOG to
a filename of your choice in the environment before starting up).
When you quit, are there objects related to thi
Boris Zbarsky wrote:
The code looks ok to me. What does the output look like if you run with
memory leak logging (in a debug build; set XPCOM_MEM_LEAK_LOG to a
filename of your choice in the environment before starting up). When
you quit, are there objects related to this stuff in the leak lo
Niky Williams wrote:
Code is below. I came across something just recently. Using the
nsIDOMNSDocument::GetBoxObjectFor (), I could possibly get and set the
same things I'm needing.
That's not threadsafe either
The code looks ok to me. What does the output look like if you run with memo
Boris Zbarsky wrote:
Niky Williams wrote:
I realize by doing it this way in a timer thread, and not within the
actual Gecko event loop, that it's probably not exactly thread safe...
It's not at all threadsafe.
but I don't believe it would be causing this issue
It sure could.
> Is there a
Niky Williams wrote:
I realize by doing it this way in a timer thread, and not
within the actual Gecko event loop, that it's probably not exactly
thread safe...
It's not at all threadsafe.
but I don't believe it would be causing this issue
It sure could.
> Is there a possible leak with ns
I've created my own Marquee type effect...the tag just wasn't
robust enough. Here is my problem. I use
nsIDOMViewCSS::GetComputedStyle () to get a reference to
nsIDOMCSSStyleDeclaration, works find and dandy, then I use
nsIDOMCSSStyleDeclaration::GetPropertyValue () to get various
propertie
