Closed
Bug 1372092
Opened 7 years ago
Closed 7 years ago
Long running Firefox eat all memory
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: szalai.kalman, Unassigned, NeedInfo)
Details
(Whiteboard: [MemShrink])
Attachments
(4 files)
User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:53.0) Gecko/20100101 Firefox/53.0 Build ID: 20170518000419 Steps to reproduce: I have several opened tabs. Actual results: During a weekend long running Firefox can eat all memory (16GB) in my machine. I upped the dom.ipc.processCount settings to 20. More custom settings are: --- Képességek Kompozitálás Direct3D 11 Aszinkron görgetés/nagyítás kerékbemenet engedélyezve WebGL-megjelenítő Google Inc. -- ANGLE (Intel(R) HD Graphics 4600 Direct3D11 vs_5_0 ps_5_0) WebGL2 megjelenítő Google Inc. -- ANGLE (Intel(R) HD Graphics 4600 Direct3D11 vs_5_0 ps_5_0) Hang háttérprogram wasapi Direct2D true DirectWrite true (6.3.9600.18592) 1. GPU Aktív Igen Leírás Intel(R) HD Graphics 4600 Gyártóazonosító 0x8086 Eszközazonosító 0x0412 Illesztőprogram verziója 10.18.14.4414 Illesztőprogram dátuma 3-23-2016 Illesztőprogramok igdumdim64 igd10iumd64 igd10iumd64 igdumdim32 igd10iumd32 igd10iumd32 Alrendszer-azonosító 309717aa RAM Unknown Diagnosztika AzureCanvasAccelerated 0 AzureCanvasBackend Direct2D 1.1 AzureCanvasBackend (UI Process) skia AzureContentBackend Direct2D 1.1 AzureContentBackend (UI Process) skia AzureFallbackCanvasBackend (UI Process) cairo Döntésnapló HW_COMPOSITING force_enabled by user: Force-enabled by pref D3D9_COMPOSITING disabled by default: Disabled by default force_enabled by user: Hardware compositing is force-enabled -- Név Firefox Verzió 53.0.3 Build az. 20170518000419 Frissítési előzmények Frissítési csatorna release User Agent Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:53.0) Gecko/20100101 Firefox/53.0 -- accessibility.lastLoadDate 1497251827 accessibility.loadedInLastSession true accessibility.typeaheadfind true accessibility.typeaheadfind.flashBar 0 browser.cache.disk.capacity 358400 browser.cache.disk.filesystem_reported 1 browser.cache.disk.hashstats_reported 1 browser.cache.disk.smart_size.first_run false browser.cache.disk.smart_size.use_old_max false browser.cache.frecency_experiment 3 browser.download.importedFromSqlite true browser.download.manager.alertOnEXEOpen true browser.download.useDownloadDir false browser.places.smartBookmarksVersion 8 browser.search.useDBForOrder true browser.sessionstore.upgradeBackup.latestBuildID 20170518000419 browser.startup.homepage_override.buildID 20170518000419 browser.startup.homepage_override.mstone 53.0.3 browser.tabs.crashReporting.includeURL true browser.tabs.remote.autostart true browser.tabs.remote.force-enable true browser.urlbar.daysBeforeHidingSuggestionsPrompt 0 browser.urlbar.lastSuggestionsPromptDate 20160912 dom.apps.lastUpdate.buildID 20161019084923 dom.apps.lastUpdate.mstone 49.0.2 dom.apps.reset-permissions true dom.ipc.plugins.asyncInit.enabled true dom.ipc.processCount 20 dom.mozApps.used true extensions.lastAppVersion 53.0.3 font.internaluseonly.changed true gfx.blacklist.direct2d.failureid FEATURE_FAILURE_DL_BLACKLIST_g984 gfx.canvas.azure.accelerated true gfx.crash-guard.d3d11layers.appVersion 49.0.2 gfx.crash-guard.d3d11layers.deviceID 0x0412 gfx.crash-guard.d3d11layers.driverVersion 10.18.14.4414 gfx.crash-guard.d3d11layers.feature-d2d true gfx.crash-guard.d3d11layers.feature-d3d11 true gfx.crash-guard.glcontext.gfx.driver-init.direct3d11-angle true gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle true gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle-force-d3d11 true gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle-force-warp true gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle-try-d3d11 true gfx.crash-guard.status. 2 gfx.crash-guard.status.d3d11layers 2 gfx.crash-guard.status.d3d11video 2 gfx.crash-guard.status.d3d9video 2 gfx.crash-guard.status.glcontext 2 gfx.offscreencanvas.enabled true layers.acceleration.force-enabled true media.benchmark.vp9.fps 227 media.benchmark.vp9.versioncheck 2 media.gmp-eme-adobe.abi x86_64-msvc-x64 media.gmp-eme-adobe.lastUpdate 1491817042 media.gmp-eme-adobe.version 16 media.gmp-gmpopenh264.abi x86_64-msvc-x64 media.gmp-gmpopenh264.lastUpdate 1473247467 media.gmp-gmpopenh264.version 1.6 media.gmp-manager.buildID 20170518000419 media.gmp-manager.lastCheck 1497251829 media.gmp-widevinecdm.abi x86_64-msvc-x64 media.gmp-widevinecdm.lastUpdate 1474471479 media.gmp-widevinecdm.version 1.4.8.903 media.gmp.storage.version.observed 1 media.hardware-video-decoding.failed false network.cookie.prefsMigrated true network.dns.disablePrefetch true network.http.speculative-parallel-limit 0 network.predictor.cleaned-up true network.prefetch-next false places.database.lastMaintenance 1497025729 places.history.expiration.transient_current_max_pages 132015 plugin.disable_full_page_plugin_for_types application/pdf plugin.importedState true plugin.state.flash 0 Expected results: Use less memory, after restart and reloading all tabs Firefox consumes about half of memory.
Reporter | ||
Comment 1•7 years ago
|
||
Reporter | ||
Comment 2•7 years ago
|
||
Comment 3•7 years ago
|
||
Mike, could you please advise related to this issue? I'm not sure if the attached reports are enough or/and what the next step forward should be.
Flags: needinfo?(mconley)
Comment 4•7 years ago
|
||
Unfortunately, the about:memory report in the pre-restart "bad" state only has the parent process listed. I'm not sure why that is, but getting an about:memory report in the bad state with all subprocesses would certainly help. That having been said, you've mentioned that you set dom.ipc.processCount to 20. Assuming you have 20+ active tabs open, loaded and running, and that you're using 20 content processes, high memory usage isn't super unexpected. I'd recommend tamping that dom.ipc.processCount back down to 4, which is the default (I believe) on Firefox 54. See http://www.erahm.org/2017/05/15/firefox-memory-usage-with-multiple-content-processes/ for details.
Flags: needinfo?(mconley)
Reporter | ||
Comment 5•7 years ago
|
||
Are these crash reports can help? Not sent: a1a0b1f7-be3c-4ecd-86f2-5412f2a426b3 17. 06. 26. 7:31 c3f7fc1a-8825-4ba6-9bc7-d81ec0a185bd 17. 06. 26. 7:31 af49ed4e-8b2e-4e91-9eda-8cdbc4274840 17. 06. 21. 8:46 523895e8-3cac-40d7-91da-c22e0a9425e4 17. 06. 21. 8:46 2b6dc6bb-7842-478d-a55b-f7b4e30d4be7 17. 06. 21. 8:46 1186a143-9966-4661-aca3-e4b3ea5eeab6 17. 06. 21. 8:46 fa6d7c71-0e3b-40c2-bb12-95ad036bd7fd 17. 06. 21. 8:45 6ec92a98-2aa0-4b0f-a440-b34f0fdcd2b6 17. 06. 21. 8:45 019e0e71-ce36-4a24-b601-681f4ccc62d3 17. 06. 21. 8:45 08ad2792-5910-42b7-aa38-6c0fed7d90d2 17. 06. 21. 8:45 095043bb-4fa7-4fff-8792-ea27d8f85550 17. 06. 21. 8:45 a13c0ecc-9731-46f2-b94f-7255366a977c 17. 06. 21. 8:45 40b59bda-43b7-4428-b428-3cc9c45823ee 17. 06. 21. 8:45 15c6a158-3a9f-40ae-81f9-2dd98e375ed7 17. 06. 21. 8:45 d689f5af-a7fd-455c-84cf-775779b18b68 17. 06. 21. 8:45 177458ff-4d58-4ef2-9b5c-967b9ae95f03 17. 06. 21. 8:45 cdf165e3-9295-4c65-b279-d3e29b43ca05 17. 06. 21. 8:39 1774cb27-7413-4347-a453-2c6eb63686c2 17. 06. 21. 8:39 9addbaff-27fb-457a-9af9-6b31f24f2888 17. 06. 20. 13:03 397329b7-2042-4548-8698-215e26c2ae35 17. 06. 19. 21:09 65006bf1-72fe-4a6d-829c-02a5c61be280 17. 06. 18. 7:26 a5100d0d-80ac-48f8-8879-ba0af52e8d99 17. 06. 13. 17:30 336cc137-2f97-4740-b8bb-da7ee8cc00df 17. 05. 30. 14:54 cd4c19c9-f174-4de3-a993-a7f174361a8f 17. 05. 24. 9:36 249fea72-532f-41d3-adbb-b63ea347d587 17. 05. 24. 9:36 9c168276-db4e-45ce-a2ba-776375e976b6 17. 05. 24. 9:35 ddc7e6fd-2508-4a30-9467-cbae0c431d28 17. 05. 24. 9:35 5627d22b-55b9-4fe0-b3fe-e36ee27930a0 17. 05. 24. 9:35 e3093e4a-0567-46bc-8450-bffa6df7fac6 17. 05. 24. 9:35 a384bedb-1542-477c-99ae-77a7880128a3 17. 05. 24. 9:35 46924cde-1d59-41a7-a550-7119827f4128 17. 05. 24. 9:35 a859a740-62f4-46aa-b9eb-932a284a2966 17. 05. 24. 9:35 fb5282ab-cdbb-4c74-8bfc-2fc0bd3b862e 17. 05. 24. 9:35 1f97fe51-bd00-4b83-bae2-9b592d1ffa2a 17. 05. 24. 9:35 b95173f1-66fd-4125-8db8-13aa56bbe354 17. 05. 24. 9:34 403ed3a1-6b05-4cc0-82a2-7450a422c3d6 17. 05. 24. 9:34 32fc3b6a-547b-4722-920b-5c723675b957 17. 05. 24. 9:34 0393978b-4627-43af-bfe6-5473fc1df57d 17. 05. 24. 9:34 325307bc-7c3a-458b-959c-b4bc893b1694 17. 05. 15. 7:49 0fc43777-066d-4c81-bab6-9a654030b3c8 17. 05. 03. 8:07 aa6b09c5-ee47-438b-ad35-94114907dd11 17. 05. 03. 8:07 746bfb35-9b8a-44e7-922b-df957eb56b82 17. 05. 03. 8:06 7cff9fa0-5486-4114-95e8-4d6ac7b2f2e8 17. 05. 03. 8:06 a6f7cf79-ed82-4545-84c3-bb653f2afb69 17. 05. 03. 8:06 fba1edae-bdee-4107-b51d-3ebb8f1321c2 17. 05. 03. 8:06 15e09925-fdcf-41c4-a1be-61a9250984ef 17. 05. 03. 8:06 d38031ae-181a-4824-bba6-dfc788bbaef4 17. 05. 03. 8:06 33530ce0-d20e-477b-9c72-8f40f53c5608 17. 05. 02. 9:23 4f857003-1e14-4c84-a520-a3336a9b85cb 17. 05. 02. 9:23 19e1448a-799a-47ca-aa8a-9ae9998f3261 17. 05. 02. 9:23 67d94120-7d3b-4d67-818b-6aa995f20dc2 17. 05. 02. 9:23 0ff5561e-533d-4f1c-ba9a-618f752cfe59 17. 05. 02. 9:23 9395b460-6fd2-4f02-a554-7c1e1e1f14f4 17. 05. 02. 9:23 612d44de-c494-47f1-b031-4b117a5f4aee 17. 05. 02. 9:23 --- Sent: bp-1b91be15-bdd8-41ba-800f-006190170626 17. 06. 26. 12:10 bp-865d0057-8ed9-499c-a3be-a07191170619 17. 06. 19. 8:08 bp-717dd1aa-c3f8-499e-a31d-1cbf01170619 17. 06. 19. 8:07 bp-fe9cb93b-dfa9-4f5e-a32a-d3f2d1170524 17. 05. 24. 9:36 bp-8baa0776-b13c-45fb-ab4e-9ddd81170508 17. 05. 08. 17:28 --
Comment 6•7 years ago
|
||
Unsent crashes are of no value :) bp-1b91be15-bdd8-41ba-800f-006190170626 @ IPCError-browser | ShutDownKill - several bug reports bp-865d0057-8ed9-499c-a3be-a07191170619 @ mozilla::a11y::IDSet::GetID - bug 1368270 bp-717dd1aa-c3f8-499e-a31d-1cbf01170619 @ mozilla::a11y::IDSet::GetID - bug 1368270 bp-fe9cb93b-dfa9-4f5e-a32a-d3f2d1170524 @ shutdownhang | google_breakpad::ExceptionHandler::WriteMinidumpOnHandlerThread bp-8baa0776-b13c-45fb-ab4e-9ddd81170508 @ nsAccessibilityService::MarkupRole > I have several opened tabs. How many?
Reporter | ||
Comment 7•7 years ago
|
||
Reporter | ||
Comment 8•7 years ago
|
||
Comment 9•7 years ago
|
||
One of the memory reports has 2GB of orphan nodes. Usually this ends up being caused by a addons or webpage that leaks DOM nodes.
Comment 10•7 years ago
|
||
Can you test with dom.ipc.processCount = 4? We don't support any other configurations than that, although we certainly want to! The next step I'll probably ask is for you to try disabling a few add-ons and seeing if that helps, as Timothy noted it looks like that might be an issue for you.
Flags: needinfo?(szalai.kalman)
Comment 11•7 years ago
|
||
Based on the lack of information from the reporter, I will mark the issue as Resolved - Incomplete.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•