516816 - Memory leak causing audio delays in quicktime playback and FCP

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[flyingmonkfilms]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3

There audio to video delays in Final Cut and Quicktime caused by a memory leak caused by Firefox when is opened in the same time with the applications. The quick fix is to close Firefox when you play or export and the delay would go away.
The problem does not come immediately when Firefox is opened but it accumulates in time, reaching a peak of close to 1 second delay after one hour when the browser is opened. It manifests such that any quicktime existing on the machine will play delayed even if FCP is not open. You move the quicktime to another machine and it plays fine there.
I remembered having this issue in another facility several weeks ago and trying to close the applications to minimize the memory usage, I fixed it by closing both opened browsers, Safari and Firefox, so I never knew which one was causing the leak. I called now the editor to check what is the status and he told me that the problem is there but everytime when he needs to play audio he closes Firefox and the delay goes away. 




Reproducible: Always

Steps to Reproduce:
1.Leave the browser opened for one hour.
2.Open Final Cut
3.OS 10.5.8 QT 7.6.2 Firefox 3.5.3
Actual Results:  
In Quicktime playback the audio is not in sync with video

Expected Results:  
It should not caused this result. The playback should be in sync.

Turn off Firefox and problem goes away.

Comment 1

[Wayne Mery (:wsmwk)]

can you reproduce this in newer firefox and quicktime?

Comment 2

[flyingmonkfilms]

Yes it does. Also we had TODAY an AE station trying to render on a Intel Mac Quad Core with 10G memory. The render stopped in the middle everytime by lack of memory!!! The only other application running was Firefox. We turned Firefox off, started again the render and the render completed......

Comment 3

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.10 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.