Bug 1576767 Comment 176 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
> I noticed that the autorelease pool is never "drained" on the compositor thread while Firefox is running.

This turns out to be false. So my patch won't help. You can stop testing with it. Sigh.

What *is* true is that `ioAccelResourceFinalize()` is never called from `_CFAutoreleasePoolPop()` on the compositor thread while Firefox is running. I'll try to figure out what significance this has, if any.
Revision 1 by
on 
> I noticed that the autorelease pool is never "drained" on the compositor thread while Firefox is running.

This turns out to be false. So my "fourth experimental patch" won't help. You can stop testing with it. Sigh.

What *is* true is that `ioAccelResourceFinalize()` is never called from `_CFAutoreleasePoolPop()` on the compositor thread while Firefox is running. I'll try to figure out what significance this has, if any.
Revision 2 by
on 
> I noticed that the autorelease pool is never "drained" on the compositor thread while Firefox is running.

This turns out to be false. So my "fourth experimental patch" won't help. You can stop testing with it. Sigh.

What *is* true is that `ioAccelResourceFinalize()` is never called from `_CFAutoreleasePoolPop()` on the compositor thread while Firefox is running, even with my patch. I'll try to figure out what significance this has, if any.

Back to Bug 1576767 Comment 176