Closed Bug 1117412 Opened 10 years ago Closed 8 years ago

Memory leak and crashes with videos on a carousel rotation

Categories

(Core :: JavaScript Engine: JIT, defect)

34 Branch
x86_64
Windows 7
defect
Not set
critical

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: masterx244, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash)

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:34.0) Gecko/20100101 Firefox/34.0 Build ID: 20141125180439 Steps to reproduce: Pinning robertsspaceindustries.com as a app-tab on a clean install of firefox 34 on Windows OS (VM was Windows 8 but i got similar behavior on WInods7 Professional) Actual results: after some hours of unattended running inside a Virtual Machine with 8GB of Ram (to simulate long running firefox-session with that tab pinned) Firefox crashed (https://crash-stats.mozilla.com/report/index/de9bef48-fe35-4f71-b685-f459f2150103). Got the suspiction that it is related to video decoder by adblocking the mp4 files on the website and haven't gotten the weird behavior Expected results: Firefox should not have crashed
(I've not tried to reproduce, but the VM-based steps make me expect that this is fairly consistent)
Blocks: SadJit
Severity: normal → critical
Component: Untriaged → JavaScript Engine: JIT
Keywords: crash
Product: Firefox → Core
Flags: needinfo?(jdemooij)
I can't reproduce this on OS X. Kannan, can you try this on Windows with Firefox 34?
Flags: needinfo?(jdemooij) → needinfo?(kvijayan)
Ok, trying to repro this now.
Flags: needinfo?(kvijayan)
I tried to replicate this for a while with firefox 34, with no luck, before I realized I have to leave it running for a while, and probably longer than a few hours since my box has more memory.
masterx, can you still reproduce on win7 with current nightly build? I was unable to reproduce
Flags: needinfo?(masterx244)
Whiteboard: [closeme 2016-07-15]
Resolved per whiteboard
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Flags: needinfo?(masterx244)
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2016-07-15]
You need to log in before you can comment on or make changes to this bug.