Closed
Bug 1095544
Opened 10 years ago
Closed 10 years ago
Lots of beach balling in Nightly
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1082849
Tracking | Status | |
---|---|---|
e10s | ? | --- |
People
(Reporter: mcote, Unassigned)
Details
Attachments
(1 file)
(deleted),
text/plain
|
Details |
I'm using today's Nightly, and I am getting a fair bit of beach balling on my MacBook Pro (OS X 10.10). Attached in a process sample during one attack.
Comment 1•10 years ago
|
||
There's CPOW traffic in here, so I suspect an add-on is misbehaving. Would you mind listing your enabled add-ons?
Flags: needinfo?(mcote)
Reporter | ||
Comment 2•10 years ago
|
||
Enabled extensions:
About sessionstore 0.3
feedly 16.0.528
Force-TLS 4.0.0
gTranslate 0.9
Heartbleed-Ext 3.0
LastPass 3.1.1
Lazarus: Form Recovery 2.3
LinkChecker 0.6.7
Mass Password Reset 1.05
PDF Viewer 1.0.277
SQLite Manager 0.8.1
uniqtabs (Unique Tabs) 0.25
Do you want Plugins listed too? I have 17 of those... Although I think I will remove a few now that I am looking at them.
Flags: needinfo?(mcote)
Comment 3•10 years ago
|
||
I'm curious to know if the beachballing goes away if you restart in safe-mode. My guess would be maybe LastPass, as it hasn't been marked fully compatible just yet (bug 1008768).
Flags: needinfo?(mcote)
Reporter | ||
Comment 4•10 years ago
|
||
Been running without addons installed; I don't think there's been any beach-balling since.
Flags: needinfo?(mcote)
Comment 5•10 years ago
|
||
Alright, well, this next bit might be a bit annoying - but it'd be good if we could narrow down which of your add-ons is the culprit.
You have two choices:
1) Bisect your add-ons to narrow down which one is causing it. This doesn't work if it's a combination of add-ons causing the problem - but my experience informs me that it's likely a single add-on causing the problem. Bisecting would take about ~4 steps.
2) Disable e10s and wait for us to instrument Nightly to tell us which add-ons are causing horrific importance (that'd be from bugs like bug 1074567 and bug 1071880).
Comment 6•10 years ago
|
||
This should get fixed by fixes in bug 1082849, where we're using LastPass as a test-case.
You need to log in
before you can comment on or make changes to this bug.
Description
•