Closed Bug 818839 Opened 12 years ago Closed 11 years ago

OOM crash when scrolling a website with heavy images

Categories

(Core :: XPCOM, defect)

Product:
Core
Component:
XPCOM
Platform:
x86
Windows 7
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: mail, Unassigned)

References

(
URL
)

Details

(Keywords: crash, reproducible)

Crash Data

Attachments

(1 file)

debug log
103.92 KB, text/plain
Details 
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:20.0) Gecko/20121205 Firefox/20.0
Build ID: 20121205030759

Steps to reproduce:

It starts up, the group had about 30 tabs, while the page loads, I closed the tab, closed 6 tabs appeared frieze window and moving to another tab, the browser is closed.


Actual results:

fell browser


Expected results:

all should be fine =((
Severity: normal → critical
Crash Signature: [@ EMPTY: no crashing thread identified; corrupt dump ]
Keywords: crash
These are OOMing in string code:
xpcom_runtime_abort(###!!! ABORT: OOM: file e:\builds\moz2_slave\m-cen-w32-ntly\build\xpcom\string\src\nsTSubstring.cpp, line 348)
I don't see any crashes with the latest build.
Update your Nightly.
Is it reproducible? If yes, does it happen in Safe Mode (see https://support.mozilla.org/kb/troubleshoot-firefox-issues-using-safe-mode)?
Flags: needinfo?(mail)
Launch Nightly 20.0 - before open tabs, check for 'Update Nightly' window pop up on the screen. If not, report the issue, because I see the updates for 'Nightly' every 2 days on and off...try to check for the updated build.

I never see this problem in Windows 7,64 OS

Detail the issue to solve better!
Thanks.
Flags: needinfo?(mail)
Flags: needinfo?(mail)
I found the instructions in the appearance of a bug, if you open a long time to scroll http://eyecandy-girls.tumblr.com/, eventually does fall with the error:
https://crash-stats.mozilla.com/report/index/bp-8146a612-f40c-45db-9998-5f72f2121210
https://crash-stats.mozilla.com/report/index/bp-a5a92922-d0cf-4152-9f26-6cade2121210
Flags: needinfo?(mail)
Check in safe mode and it flew https://crash-stats.mozilla.com/report/index/bp-16180db3-e716-4038-aea3-5c88b2121210 but much longer I had to scroll the page. Perhaps this is due to the fact that, along with Adblock it quickly becomes clogged.
Depends on: 722083
Summary: crashes when working with tabs → [OOM? null dump] crashes when working with tabs
(In reply to adminnu from comment #8)
> Check in safe mode and it flew
> https://crash-stats.mozilla.com/report/index/bp-16180db3-e716-4038-aea3-
> 5c88b2121210 but much longer I had to scroll the page.
There's no OOM in this case.

(In reply to adminnu from comment #9)
> https://crash-stats.mozilla.com/report/
> list?signature=EMPTY%3A+no+crashing+thread+identified%3B+corrupt+dump
This crash signature is meaningless. It just means Firefox crashes in an unknown location.

Please provide a stack trace (see https://developer.mozilla.org/docs/How_to_get_a_stacktrace_with_WinDbg).
Flags: needinfo?(mail)
Keywords: stackwanted
Crash Signature: [@ EMPTY: no crashing thread identified; corrupt dump ]
No longer depends on: 722083
Please leave this signature on the bug, it's one case that triggers crashes with that null dump signature, so we really want it to be connected with it. Something happens there so that the Windows function to generate a minidump fails - you're right that this isn't helpful in telling us what happened, but it's still info I want to have tracked.
Crash Signature: [@ EMPTY: no crashing thread identified; corrupt dump ]
Of course, the initial departure was due to another, now try to scrolling.
Flags: needinfo?(mail)
Attached file debug log — 
hope to do it right
(In reply to adminnu from comment #7)
> I found the instructions in the appearance of a bug, if you open a long time
> to scroll http://eyecandy-girls.tumblr.com/, eventually does fall with the
> error:
It crashes for me also: bp-fdc02ab8-5156-45f7-bd95-aec002121210.

(In reply to adminnu from comment #13)
> hope to do it right
It seems good. It has the same signature as bug 764342.
Blocks: 764342
Status: UNCONFIRMED → NEW
Crash Signature: [@ EMPTY: no crashing thread identified; corrupt dump ] → [@ EMPTY: no crashing thread identified; corrupt dump ] [@ mozalloc_abort(char const* const) | mozalloc_handle_oom(unsigned int) | moz_xmalloc | nsSegmentedBuffer::AppendNewSegment()]
Component: Untriaged → XPCOM
Ever confirmed: true
Keywords: stackwanted → reproducible
Product: Firefox → Core
Hardware: x86_64 → x86
Summary: [OOM? null dump] crashes when working with tabs → OOM crash when scrolling a website with heavy images
Version: 20 Branch → Trunk
Does it happen in today's nightly that contains the fix of bug 689623?
Flags: needinfo?(mail)
(In reply to Scoobidiver from comment #15)
> Does it happen in today's nightly that contains the fix of bug 689623?

WFM with 23.0a1 (2013-05-13)
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(mail)
Resolution: --- → WORKSFORME
adminnu can you still reproduce crash?


(In reply to Wayne Mery (:wsmwk) from comment #16)
> (In reply to Scoobidiver from comment #15)
> > Does it happen in today's nightly that contains the fix of bug 689623?
> 
> WFM with 23.0a1 (2013-05-13)

WFM meaning I don't crash. But it still sucks memory
Flags: needinfo?(mail)
Played around with the site, it definitely does use a lot of memory, but it does not appear to be due to decoded image data.
Flags: needinfo?(mail)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: