Closed Bug 1384454 Opened 8 years ago Closed 4 years ago

Intermittent dom/tests/mochitest/crypto/test_getRandomValues.html | application crashed [@ nsThreadSyncDispatch::Run()] after Assertion failure: ((bool)(!!(!NS_FAILED_impl(result)))) (task in sync dispatch should not fail), at nsThreadSyncDispatch.h:41

Categories

(Core :: XPCOM, defect)

defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox-esr52 --- unaffected
firefox55 --- unaffected
firefox56 --- affected
firefox57 --- affected

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

(Keywords: assertion, crash, intermittent-failure)

Crash Data

Win7 reftests are hitting this assert pretty frequently on Beta since Wednesday's uplift of 56 to it. Can you please take a look, Nathan?
Flags: needinfo?(nfroyd)
Component: DOM → XPCOM
Keywords: assertion
It looks like Preferences are complaining that we're failing to write the preference file out at shutdown. I don't know why this would have increased because of Beta, nor do I know why it's specific to Win7 reftests. I think we *could* just remove the assertion that's falling over, or make the preferences runnable stop complaining about failure, but I'd really appreciate understanding why things are failing in the first place.
Flags: needinfo?(nfroyd)
Interesting that it's preferences related, given bug 1386263!
(In reply to Ryan VanderMeulen [:RyanVM] from comment #4) > Interesting that it's preferences related, given bug 1386263! FWIW, it's going through the same codepath (SavePrefFileBlocking) from that bug, but it's not getting called from GFX code. I wonder if we changed that preferences code somehow during the 56 cycle...?
(In reply to Nathan Froyd [:froydnj] from comment #5) > (In reply to Ryan VanderMeulen [:RyanVM] from comment #4) > > Interesting that it's preferences related, given bug 1386263! > > FWIW, it's going through the same codepath (SavePrefFileBlocking) from that > bug, but it's not getting called from GFX code. I wonder if we changed that > preferences code somehow during the 56 cycle...? We certainly did! It's the suspect origin bug from 1386263: bug 789945.
Looks like this went away as expected after the pref flip from bug 1386263.
Bug 1388464 should have the actual fix.
See Also: → 1388464

Moving these bugs (intermittent test failures with crashes) out of P5.

Priority: P5 → --

It seems this crash no longer occurs since I cant find any reports on it , I will close it as WFM and then if it starts to reoccur we can reopen the issue

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.