Closed
Bug 921863
Opened 11 years ago
Closed 11 years ago
Out of memory crash
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: noragen, Unassigned)
Details
(Keywords: crash, Whiteboard: [needs safe mode test])
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.76 Safari/537.36
Steps to reproduce:
Sorry, can't say exactly, I've run Firefox with two windows, normal and privacy.
But in normal mode it made already some graphic-errors when painting.
Some regions were black.
But crash, it seems, was in privacy window.
Actual results:
Crash. I have a no idea how to reproduce. But it seems it is a memory problem.
Memory at top-level-stack:
+ msg 0x19d3f984 "out of memory: 0x0000000000394F98 bytes requested" const char * const
Here is memory dump "firefox-memory-error.dmp.xz" (290.3 MB) compressed via 7zip:
https://mega.co.nz/#!3Rk01IjI!C70yoDKvWX93B8OO8Dc6zzQXz1VnzySDO5rkHvxH14k
And here the stack-trace:
mozalloc.dll!mozalloc_abort(const char * const msg=0x19d3f984) Line 30 C++
> mozalloc.dll!mozalloc_handle_oom(unsigned int size=3755928) Line 50 + 0x9 bytes C++
mozalloc.dll!moz_xmalloc(unsigned int size=3755928) Line 56 + 0x6 bytes C++
xul.dll!nsTArray_base<nsTArrayInfallibleAllocator,nsTArray_CopyElements<nsWeakFrame> >::EnsureCapacity(unsigned int capacity=0, unsigned int elemSize=433322484) Line 119 + 0x15 bytes C++
xul.dll!nsTArray_Impl<mozilla::safebrowsing::AddPrefix,nsTArrayInfallibleAllocator>::SetCapacity(unsigned int capacity=469490) Line 1331 C++
xul.dll!mozilla::safebrowsing::HashStore::ReadAddPrefixes() Line 712 C++
xul.dll!mozilla::safebrowsing::HashStore::ReadHashes() Line 394 C++
xul.dll!mozilla::safebrowsing::HashStore::BeginUpdate() Line 413 C++
mozglue.dll!arena_dalloc(void * ptr=0x28af0c40, unsigned int offset=0) Line 4680 C
mozglue.dll!je_free(void * ptr=0x00000000) Line 6601 C
mozglue.dll!arena_dalloc(void * ptr=0x056ee740, unsigned int offset=0) Line 4680 C
xul.dll!nsRunnableMethodImpl<enum tag_nsresult (__stdcall nsIUrlClassifierDBService::*)(void),1>::Run() Line 351 C++
xul.dll!nsThread::ProcessNextEvent(bool mayWait=true, bool * result=0x19d3fb74) Line 632 C++
xul.dll!nsThread::ThreadFunc(void * arg=0x1c1d0c10) Line 264 + 0x1d bytes C++
nss3.dll!pr_root(void * arg=0x1c1d0c10) Line 90 + 0xd bytes C
msvcr100.dll!_callthreadstartex() Line 314 + 0x6 bytes C
msvcr100.dll!_threadstartex(void * ptd=0x00684c28) Line 292 + 0x5 bytes C
kernel32.dll!@BaseThreadInitThunk@12() + 0x12 bytes
ntdll.dll!___RtlUserThreadStart@8() + 0x27 bytes
ntdll.dll!__RtlUserThreadStart@8() + 0x1b bytes
Expected results:
no memory error, no crash
Comment 1•11 years ago
|
||
happens in safe mode?
http://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode
here you see the gui from firefox some time before it was crashing
Here is a brand new memory dump from firefox javascript crash in safemode:
firefox-safemode-out-of-memory-javascript-crash.dmp.xz (312.3 MB)
https://mega.co.nz/#!2AF1DbRI!WEMJPFcm4mJOrgBaAonQGQoGVAMD3FfvLv3SLF9PFVM
Comment 5•11 years ago
|
||
Thanks!
This bug occurs for me at least once or twice a day. It can be provoked using extensively Javascript, for example the new google maps forcing this. The crash comes not instantly, but after a longer while.
Now where I gave you all information about it, please fix that beast and take a look over the memory management! It is really really really really REALLY annoying! ;) Thanks!
Updated•11 years ago
|
If testcase is needed, go to new Google maps and click around. It can take several time, until firefox crashes, but it will! Sometimes it takes longer, sometimes it is faster. And don't remove importance, this is more important than to implement other unnecessary unneeded features, don't close the tabs after end of a firefox session, let restore them after next start, do this with some hundred websites! Ensure that there is still enough RAM. Memory management has to be 100% correct or you will run into problems everywhere!
Flags: needinfo?(noragen)
Priority: -- → P1
Updated•11 years ago
|
Priority: P1 → --
Comment 8•11 years ago
|
||
Below are your crashes from the past 3 months. [1] I'm not sure any of them are helpful, except that one cites http://www.lightinthebox.com/de/trompete-meerjungfrau-spaghetti-traegern-tuell-hochzeitskleid_p604668.html?currency=EUR&litb_from=paid_adwords_shopping&gclid=CIfCofew-rkCFYWz3godWDEALQ which has many images.
Your attached dump shows many js warnings of the type
[JavaScript Warning: "Fehler beim Verarbeiten des Wertes für 'filter'. Deklaration ignoriert." {file: "https://www.google.de/search?q=green+coffee+Einnahme&ie=utf-8&oe=utf-8&rls=org.mozilla:de:official&client=firefox-a&gws_rd=cr&ei=mAZLUpnGHMTfsgbf6oHoBQ"
shortly followed by OOM js error, etc...
[JavaScript Error: "[Exception... "'out of memory' when calling method: [nsIObserver::observe]" nsresult: "0x8057001e (NS_ERROR_XPC_JS_THREW_STRING)" location: "native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0" data: no]"]
[JavaScript Error: "ReferenceError: loadDetailSearchInfo is not defined" {file: "http://www.locationguide24.com/location-suchen/veranstaltungsraum/Location///list.html?tx_dllocationguide_pi1%5Bort%5D=M%C3%BCnchen&tx_dllocationguide_pi1%5Bland%5D=&tx_dllocationguide_pi1%5Bbundesland%5D=&tx_dllocationguide_pi1%5Bumkreis%5D=50&tx_dllocationguide_pi1%5Blocationid%5D=Name+o.+ID&gclid=CP-a_feT4rkCFQy33god-3MAUA" line: 3235}]
[JavaScript Warning: "SyntaxError: 08 is not a legal ECMA-262 octal constant" {file: "http://www.locationguide24.com/lg24/js/lib/mootools-core-1.4.4-full-compat-yc.js" line: 503 column: 60 source: ":10,SPECIAL23KEY:12,SPECIAL5KEY:9,SPECIAL19KEY:5,DEFAULTKEY:08})"}]
[JavaScript Warning: "SyntaxError: 09 is not a legal ECMA-262 octal constant" {file: "http://www.locationguide24.com/lg24/js/lib/mootools-core-1.4.4-full-compat-yc.js" line: 503 column: 60 source: "EY:3,SPECIAL23KEY:8,SPECIAL5KEY:3,SPECIAL19KEY:7,DEFAULTKEY:09})"}]
[JavaScript Error: "TelemetryStopwatch: key "FX_SESSION_RESTORE_SERIALIZE_DATA_MS" was already initialized" {file: "resource://gre/modules/TelemetryStopwatch.jsm" line: 53}]
[JavaScript Error: "TelemetryStopwatch: key "FX_SESSION_RESTORE_SERIALIZE_DATA_LONGEST_OP_MS" was already initialized" {file: "resource://gre/modules/TelemetryStopwatch.jsm" line: 53}]
[JavaScript Error: "[Exception... "'out of memory' when calling method: [nsIObserver::observe]" nsresult: "0x8057001e (NS_ERROR_XPC_JS_THREW_STRING)" location: "native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0" data: no]"]
[JavaScript Warning: "Fehler beim Verarbeiten des Wertes für 'background-image'. Deklaration ignoriert." {file: "https://plus.google.com
Also interesting that you crash Thunderbird [2] (which you should update to version 24), which perhaps suggests the crash cause is something like antivirus software.
Beyond that, you really should try running Firefox in safe mode for a day...
(In reply to Wayne Mery (:wsmwk) from comment #1)
> happens in safe mode?
> http://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode
please run in safe mode for a day
And please do not set bug priority - priority is for developers.
[1] https://crash-stats.mozilla.com/search/?email=~noragen&date=%3E2013-10-01&date=%3C2013-12-25&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform
[@ EMPTY: no crashing thread identified; corrupt dump] - Firefox 24.0 BP-55985c84-b49a-48e9-9d09-d3d202131003
[@ EMPTY: no crashing thread identified; corrupt dump] - Firefox 24.0 BP-2c881a9f-2044-44e8-9986-fdcc02131003
[@ EMPTY: no crashing thread identified; corrupt dump] - Firefox 25.0 BP-7559a0c6-fb6c-4210-b699-343212131110
[@ _chkstk | WPP_SF_] - Firefox 27.0a1 BP-6af4294b-7cc9-4129-82ea-9fa962131022
[@ mozalloc_abort(char const* const) | xul.dll@0xdd6788 | xul.dll@0x8a686b | xul.dll@0x6aea28 | xul.dll@0xc3138 | xul.dll@0xe70e6 | js::Invoke(JSContext*, JS::Value const&, JS::Value const&, unsigned int, JS::Value*, JS::MutableHandle<JS::Value>)] - Firefox 25.0 BP-2cbbf072-6a35-4473-8678-5b5372131103
[@ mozalloc_abort(char const* const) | xul.dll@0xdd6788 | xul.dll@0x8a686b | xul.dll@0x6aea28 | xul.dll@0xc3138 | xul.dll@0xe70e6 | js::Invoke(JSContext*, JS::Value const&, JS::Value const&, unsigned int, JS::Value*, JS::MutableHandle<JS::Value>)] - Firefox 25.0 BP-7e1e4da8-d36c-4ee4-8748-0cbba2131106
[@ mozalloc_abort(char const* const) | xul.dll@0xdd6788 | xul.dll@0x8a686b | xul.dll@0x6aea28 | xul.dll@0xc3138 | xul.dll@0xe70e6 | js::Invoke(JSContext*, JS::Value const&, JS::Value const&, unsigned int, JS::Value*, JS::MutableHandle<JS::Value>)] - Firefox 25.0 BP-b0c73c19-14d1-4175-9a71-fb34f2131107
[2] [@ EMPTY: no crashing thread identified; ERROR_NO_MINIDUMP_HEADER] - Thunderbird 17.0.8 Crash Report - Report ID: 3ae13bb1-7975-40db-b0fe-4e6e52131215
Flags: needinfo?(noragen)
Priority: P1 → --
Summary: Out of memory crash (with dmp) → Out of memory crash
Whiteboard: [needs safe mode test]
I have a similar problem (27.0.1 on Linux i386): Normally, my FF consumes around 1300MB, using three windows with ~200-250 tabs. Now I wanted to load a lenghty thread from Twitter, which happens to have at least several hundred tweets. I could not load it in its entirety, because memory usage kept increasing, and after coming close to 2000MB, the browser crashed. I tried two times, but due to the awful Twitter UI, it took me more than an hour to scroll that far down, one screenful at a time (still did not hit the bottom...), and after that, I gave up.
I have no limits and set, and I have enough RAM to let FF grow to at least 3GB. There appears to be no 64 bit version of FF, right?
Comment 10•11 years ago
|
||
be great if you get a crash ID in safe mode
Whiteboard: [needs safe mode test] → [closeme 2014-05-01][needs safe mode test]
Comment 11•11 years ago
|
||
Resolved per whiteboard
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Flags: needinfo?(noragen)
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2014-05-01][needs safe mode test] → [needs safe mode test]
Updated•9 years ago
|
Keywords: testcase-wanted
You need to log in
before you can comment on or make changes to this bug.
Description
•