Closed Bug 681205 Opened 8 years ago Closed 8 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:8.0a2) Gecko/20110822 Firefox/8.0a2 Build ID: 20110822042002 Steps to reproduce: Opening 20+ tabs at once leads after a while in FF6 taking over 1GB of memory, unresponsive and leads to the same crashes Actual results: Opened 20+ tabs (see the set bellow), FF6 took over 1.2GB of memory, plugin-container over 400MB, and become unresposive. After 5+ minutes it started responsing (see about:memory screenshot from that moment) and was working for some more minutes. Then crashed with usual bp-76c62519-b403-4121-aa8a-aefdb2110822 Set of bookmarks bellow can be used to reproduce this behaviour. http://www.adverbox.com/ http://www.adforum.com/index.asp http://adweek.blogs.com/ http://adverlicio.us/ http://adland.tv/ http://designyoutrust.com/ http://adage.com/ http://www.coloribus.com/ http://adverlab.blogspot.com/ https://www.behance.net/ http://www.ibelieveinadv.com/ http://www.adrants.com/ http://www.notcot.com/ http://medialne.etrend.sk/reklama.html http://creativity-online.com/ http://theinspirationroom.com/daily/ http://www.brandweek.com/bw/index.jsp http://cyanatrendland.com/ http://www.marketingprofs.com/ http://liveanduncensored.com/ http://www.illegaladvertising.com/ http://www.mediabistro.com/agencyspy/ http://www.copyranter.blogspot.com/ http://scaryideas.com/ http://adsoftheworld.com/
Assignee: nobody → general
Severity: normal → critical
Crash Signature: [@ js::MaybeGC(JSContext*) ]
Product: Firefox → Core
QA Contact: general → general
Daniel: Are you running with any Addons installed?
Yes Marcia, cannot be list seen in bp-76c62519-b403-4121-aa8a-aefdb2110822 Tried some time ago to run without, had the same problem, but after much longer time.
(In reply to Daniel Dočekal from comment #2) > Yes Marcia, cannot be list seen in bp-76c62519-b403-4121-aa8a-aefdb2110822 > > Tried some time ago to run without, had the same problem, but after much > longer time. Is this problem repeatable? I just tried in Nightly and it's kind of slow but doesn't lock up or crash. How much system memory do you have? Is it unresponsive because it starts swapping? This smells like an OOM crash but I'm not sure.
> Is this problem repeatable? Yes David, in classic Firefox it's repeatable by just using it. Or even by just leaving it running for hours. Had crash in Aurora just now - https://crash-stats.mozilla.com/report/index/bp-12b0e642-30e7-43c8-b408-1afc92110829 - in the same moment. Just opened bookmarks (Open All In Tabs). Seems Aurora is crashing less (did not crash for some 3-4 days, normal Firefox can crash 2-3 times a day with this).
> How much system memory do you have? 3GB and around 500MB-1GB is still free at time of crash. > Is it unresponsive because it starts swapping? Nope. Usually half gig o memory is available. When FF goes over 1GB of memory, Paged set is still only around 300KB (pretty constant actually)
This may be a dupe of bug 633845, which has the same signature on it.
I cannot reproduce this bug using Windows 7 and Mozilla/5.0 (Windows NT 6.1; rv:10.0a1) Gecko/20111028 Firefox/10.0a1
Mozilla/5.0 (Windows NT 6.1; rv:11.0a1) Gecko/20111127 Firefox/11.0a1 I could not reproduce the crash mentioned in this bug, but still experienced low responsiveness. Also, another crash occured, for which bug #706096 was logged. Reporter, are you still able to reproduce the initial issue? Thank you!
Sorry Mihaela, could not continue using Firefox, number of crashes and sluggish response were not at acceptable level anymore. Now on Chrome, not crashing, nothing sluggish. (In reply to Mihaela Velimiroviciu [QA] from comment #8) > Mozilla/5.0 (Windows NT 6.1; rv:11.0a1) Gecko/20111127 Firefox/11.0a1 > > I could not reproduce the crash mentioned in this bug, but still experienced > low responsiveness. Also, another crash occured, for which bug #706096 was > logged. > > Reporter, are you still able to reproduce the initial issue? > > Thank you!
Resolving as incomplete since no further info was provided.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.