Closed Bug 1229272 Opened 7 years ago Closed 7 years ago

Intermittent e10s browser_storage_sidebar.js | Uncaught exception - at :0 - Error: operation not possible on dead CPOW

Categories

(DevTools :: Storage Inspector, defect)

Product:
DevTools
Component:
Storage Inspector
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(e10s+, firefox45 affected, firefox47 fixed, firefox48 fixed)

Status:
RESOLVED FIXED
Milestone:
Firefox 48
Tracking Flags:
Tracking Status
e10s + ---
firefox45 --- affected
firefox47 --- fixed
firefox48 --- fixed

People

(Reporter: philor, Assigned: ochameau)

References

(Blocks 1 open bug)

Details

(Keywords: intermittent-failure)

Attachments

(1 file)

Stop using CPOW when creating indexed DB in storage tests.
3.16 KB, patch
miker
: review+
Details | Diff | Splinter Review
Summary: Intermittent browser_storage_sidebar.js | Uncaught exception - at :0 - Error: operation not possible on dead CPOW → Intermittent e10s browser_storage_sidebar.js | Uncaught exception - at :0 - Error: operation not possible on dead CPOW
Blocks: e10s-tests
tracking-e10s: --- → +
Alexander, do you have any ideas about this one?  It seems to have gotten worse recently, so was wondering if it was related to your cache storage panel changes.
Flags: needinfo?(poirot.alex)
Congratulations, you're our top actual and still-enabled intermittent. Your prize is an overly-detailed skip-if, since there's only been one win7 debug, all the rest have been opt.
Keywords: leave-open
Whiteboard: [test disabled on e10s Win7 opt]
Component: Developer Tools → Developer Tools: Storage Inspector
While I was looking at bug 1229272, I found this possible improvement...
Comment on attachment 8724720 [details] [diff] [review]
Stop using CPOW when creating indexed DB in storage tests.

The change in clear() call prevents some warning messages.
And I believe the change in call to setup() fixes this intermittent.
But I'm never sure about the intermittents being really fixed now...
Flags: needinfo?(poirot.alex)
Attachment #8724720 - Flags: review?(mratcliffe)
Assignee: nobody → poirot.alex
Comment on attachment 8724720 [details] [diff] [review]
Stop using CPOW when creating indexed DB in storage tests.

Review of attachment 8724720 [details] [diff] [review]:
-----------------------------------------------------------------

(In reply to Alexandre Poirot [:ochameau] from comment #14)
> Comment on attachment 8724720 [details] [diff] [review]
> Stop using CPOW when creating indexed DB in storage tests.
> 
> The change in clear() call prevents some warning messages.
> And I believe the change in call to setup() fixes this intermittent.
> But I'm never sure about the intermittents being really fixed now...

Until a test has run when the try servers are under high load we never really know... chaos mode helps a lot though.
Attachment #8724720 - Flags: review?(mratcliffe) → review+
Mike, can you find anybody to carry on the torch here? This is almost a permafailure on Win 7 debug. If you need someone to push to Try during the the weekend, let me know.
Flags: needinfo?(mratcliffe)
See Also: → 1253511
Whiteboard: [test disabled on e10s Win7 opt] → [test disabled on Windows e10s]
I believe that Alex's change fixes this.
Flags: needinfo?(mratcliffe)
Try seems to say it is being fixed, I launched some new runs.
But there is a suspicious intermittent:
TEST-UNEXPECTED-FAIL | leakcheck | default process: 792 bytes leaked (CEnumFormatEtc, CondVar, LazyIdleThread, Mutex, nsDataObj, ...)

But it seems to be bug 1222979.
fx-team is closed, but I'll try to push this patch once it reopens.
https://hg.mozilla.org/integration/fx-team/rev/571fa014bb35a2026fef866abe08daa52e599a46
Bug 1229272 - Stop using CPOW when creating indexed DB in storage tests. r=mratcliffe
Keywords: leave-open
Whiteboard: [test disabled on Windows e10s]
https://hg.mozilla.org/mozilla-central/rev/571fa014bb35
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox48: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 48
Whiteboard: [checkin-needed-aurora]
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.