Closed Bug 1134858 Opened 5 years ago Closed 5 years ago
crash with OOM after startup with Tracking Protection enabled
This bug was filed from the Socorro interface and is report bp-07cfd0a5-db1e-493b-b270-69e3c2150219. ============================================================= Also https://crash-stats.mozilla.com/report/index/003542fd-98ca-493e-8b75-78e062150219 and https://crash-stats.mozilla.com/report/index/003542fd-98ca-493e-8b75-78e062150219 I was using my normal profile as usual, when all of a sudden while playing a video the browser locked up and then crashed. It now always crashes shortly after startup (about 30 seconds) with OOM.
Gian-Carlo or Monica, what can I do to help you out here? This crash is preventing me from using my default profile.
Video of the crash and memory consumption, showing nothing out of the ordinary: http://screencast.com/t/Nqfa92Rdf Same thing happens when restarting in Safe Mode
Can anyone verify if this bug is happening in release?
I had this happen multiple times nightly.. I disabled the about config tracking protection prefs (via editing my prefs file when crashed) and haven't seen one since.
I sent mail to my Google contacts and pointed them at this bug. FYI, catlee reported on #developers that release was hanging as well. I am trying to get more information on release crashes.
I was not seeing this, but turning on Tracking Protection crashed me almost immediately. I turned it back off and things are fine again.
re-enabling TP made the problem recur (still nightly) - so its determinstic for me. I'll try release.
It seems to be TP. I disabled privacy.trackingprotection.enabled and the crashes have stopped. I was getting them on my Mac (Firefox Beta) and my Linux box (a trunk build from a few weeks ago). Both had TP enabled. Some crashes from Linux: https://crash-stats.mozilla.com/report/index/bp-7d89a8b6-84f5-40d8-bae3-a7e112150219 https://crash-stats.mozilla.com/report/index/bp-cc43851c-5a42-4787-83f4-db68d2150219 https://crash-stats.mozilla.com/report/index/bp-9531ccfb-4f04-47de-a005-406072150219 https://crash-stats.mozilla.com/report/index/bp-1a80c3e1-2fe4-4b5a-972a-07ae22150219 https://crash-stats.mozilla.com/report/index/bp-c3964a73-73d8-4830-9322-ca4352150219
Summary: crash with OOM after startup in Safe Browsing → crash with OOM after startup with Tracking Protection enabled
This is not a Google issue, this is ours. It only affects people who have tracking protection enabled, and we pushed a server update today. For now the workaround is to disable tracking protection. We will figure out how to fix or revert the server.
confirm that it impacts my profile in release too.
I filed bug 1134885 for client-side robustness against broken updates.
https://crash-stats.mozilla.com/signature/?signature=OOM+|+large+|+NS_ABORT_OOM%28unsigned+long%29+|+nsTArray_base%3CnsTArrayInfallibleAllocator%2C+nsTArray_CopyWithMemutils%3E%3A%3AEnsureCapacity%28unsigned+long%2C+unsigned+long%29+|+mozilla%3A%3Asafebrowsing%3A%3AChunkSet%3A%3ASet%28unsigned+int%29&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&page=1 Shows OOM crash reports from 35.0.1 through 38.0a1
If I understood the problem correctly, the crashes will stop as soon as the server is fixed and the clients *won't* be stuck with a corrupted database or something like that. The crashed happened shortly after startup because that's when Firefox probes for updates.
The server rollback is complete and it will take a little while for DNS to catch up after the rollback. Please let me know if this fix didn't work.
Enough people have reported back that the rollback worked that I will mark as fix. There will be a postmortem coming.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Crash Signature: , nsTArra...] → , nsTArra...] [@ OOM | large | mozalloc_abort(char const* const) | mozalloc_handle_oom(unsigned int) | moz_xrealloc | nsTArray_base<nsTArrayInfallibleAllocator, nsTArray_CopyWithMemutils>::EnsureCapacity(unsigned int, unsigned int) | nsTArray_Impl<mozill…
Crash Signature: , unsigned int) | nsTArray_Impl<mozilla::net::nsHttpT... ] → , unsigned int) | nsTArray_Impl<mozilla::net::nsHttpT... ] [@ OOM | large | NS_ABORT_OOM(unsigned long) | nsTArray_base<nsTArrayInfallibleAllocator, nsTArray_CopyWithMemutils>::EnsureCapacity(unsigned long, unsigned long) | mozilla::safebrowsing::ChunkSe…
You need to log in before you can comment on or make changes to this bug.