1232754 - Memory leak at TweakTown + High CPU usage

Status: RESOLVED INCOMPLETE

(Core Graveyard :: Plug-ins, defect)

Description

[smeker21]

Attachment: TweakTownLeak.png

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0
Build ID: 20151029151421

Steps to reproduce:

Opened 6 tabs on TewakTown.com(as shown in the screenshot) and firefox becomes unresponsive after a few minutes as well as using too much memory.
Bug can be reproduced multiple times. Happens on older firefox versions too.

OS: Win 8.1 with all updates
CPU: i5-3570k
RAM: 8GB
GPU: Radeon 280X 4Gb with Crimson driver v15.11


Actual results:

Firefox becomes unresponsive after a few minutes and using too much memory.

Comment 1

[ovidiu boca[:Ovidiu]]

 Build ID  20151217072309
 User Agent  Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:46.0) Gecko/20100101 Firefox/46.0

Hi, 
I have tested this problem on Win 8.1 x64 with FF Nightly 46.0a1 and I can't reproduce the unresponsive behaviour and the memory usage, the CPU was 32% at his higher level. 

Please download the Firefox Nightly from here: https://nightly.mozilla.org/ and retest the problem.
Also please create a new profile, you have the steps here:https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles?redirectlocale=en-US&redirectslug=Managing-profiles#w_starting-the-profile-manager

Please test if the issue can be reproduced in the safe mode of Firefox: https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode

Comment 2

[smeker21]

(In reply to ovidiu boca from comment #1)
>  Build ID  20151217072309
>  User Agent  Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:46.0)
> Gecko/20100101 Firefox/46.0
> 
> Hi, 
> I have tested this problem on Win 8.1 x64 with FF Nightly 46.0a1 and I can't
> reproduce the unresponsive behaviour and the memory usage, the CPU was 32%
> at his higher level. 
> 
> Please download the Firefox Nightly from here: https://nightly.mozilla.org/
> and retest the problem.
> Also please create a new profile, you have the steps
> here:https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-
> firefox-profiles?redirectlocale=en-US&redirectslug=Managing-
> profiles#w_starting-the-profile-manager
> 
> Please test if the issue can be reproduced in the safe mode of Firefox:
> https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-
> mode

Hi,
No problem with FF nightly 46.0a1. With 7 tabs memory at 260MB.
With new profile on FF 43x64 memory at around 2GB after a couple of mins and very sluggish.
With safe mode on FF 43x64 memory at around 2GB after a couple of mins and very sluggish.
Same tabs opened on all versions.

Comment 3

[ovidiu boca[:Ovidiu]]

Hi, 

I have tested again on Win 8.1 with Firefox 43 version, with new profile and everything works as expected.

Comment 4

[smeker21]

Dunno then.

Tried Firefox 44beta1 64bit and all OK. 7 tabs on TweakTown and memory at around 250MB.

Firefox 43.0.1 64bit 7tabs and memory at 2GB after few mins?

Will try an upgrade to 44 once it's out and see. 
If it's the same then I'll try a clean install of 44.

Comment 5

[ovidiu boca[:Ovidiu]]

Hi, 
Please let us know if that solved your problem. 
Thank you for your time.

Comment 6

[smeker21]

OK, so the problem is in the plugin container.
In ff44 firefox process blows up to 3GB RAM usage and becomes unresponsive.
In ff47 firefox process stays at 300MB and is responsive while the separate plugin container process blows up to 3GB RAM usage.
As far as I can tell it's cause ff47 has multi process enabled by default.
I can't turn multi process on in ff44.

Comment 7

[ovidiu boca[:Ovidiu]]

Hi and thank you for your feedback.
As far as I know only Firefox Nightly has multi process feature, it's not present in released versions for now. I also retested this and I can't reproduce it. Based on your comment I will change the component.

Comment 8

[Benjamin Smedberg]

Unfortunately it seems that even if this problem persists, we don't have enough information to actually do something about it. I agree this sucks, but I'm going to close this bug report for lack of actionable next steps.