Closed Bug 1620477 (fission-crashtests) Opened 4 years ago Closed 4 years ago

[meta] Fix crashtest fission failures

Categories

(Core :: DOM: Content Processes, defect, P2)

defect

Tracking

()

RESOLVED FIXED
Fission Milestone M6a

People

(Reporter: tnikkel, Unassigned)

References

Details

(Keywords: meta, Whiteboard: fission-tests)

No description provided.

Summary that I made for myself last week (so some of these could be fixed now) based on disabling tests so I could get a usable crashtest to test my reftest harness changes on try. Some of these have more than one failure mode/crash address and I include them all.

dom/base/crashtests/607222.html
crashes intermittently
application crashed [@ mozilla::dom::ClientSource::WindowExecutionReady(nsPIDOMWindowInner*)]

docshell/base/crashtests/1331295.html
consistently crashes
application crashed [@ mozilla::dom::ContentParent::RecvCacheBrowsingContextChildren(mozilla::dom::MaybeDiscarded<mozilla::dom::BrowsingContext> const&)]
Assertion failure: ChildID() == aBC->GetInFlightProcessId() (Attempt to modify a BrowsingContext from a child which doesn't own it), at /builds/worker/workspace/build/src/dom/ipc/ContentParent.cpp:5976
application crashed [@ mozilla::dom::ContentParent::CheckBrowsingContextOwnership(mozilla::dom::CanonicalBrowsingContext*, char const*) const]
[Child 1378, Main Thread] ###!!! ASSERTION: Overwriting an existing document channel!: '(loadFlags & nsIChannel::LOAD_REPLACE) || !(mDocumentRequest.get())', file /builds/worker/workspace/build/src/uriloader/base/nsDocLoader.cpp, line 428
[Child 1378, Main Thread] ###!!! ASSERTION: Wrong Document Channel: 'request == mDocumentRequest', file /builds/worker/workspace/build/src/uriloader/base/nsDocLoader.cpp, line 1500

dom/base/crashtests/610571-1.html
consistently crashes
application crashed [@ mozilla::dom::ContentParent::RecvAttachBrowsingContext(mozilla::dom::BrowsingContext::IPCInitializer&&)]

layout/generic/crashtests/471360.html
consistently crashes
application crashed [@ mozilla::dom::ClientSource::WindowExecutionReady(nsPIDOMWindowInner*)]
application crashed [@ mozilla::dom::ContentParent::RecvCacheBrowsingContextChildren(mozilla::dom::MaybeDiscarded<mozilla::dom::BrowsingContext> const&)]
Assertion failure: IsCurrentInnerWindow(), at /builds/worker/workspace/build/src/dom/base/nsGlobalWindowInner.cpp:5341
Assertion failure: !contentParent->IsDead(), at /builds/worker/workspace/build/src/dom/ipc/ContentParent.cpp:949
application crashed [@ nsGlobalWindowInner::SyncStateFromParentWindow()]
application crashed [@ mozilla::dom::ContentParent::GetNewOrUsedBrowserProcessAsync(mozilla::dom::Element*, nsTSubstring<char16_t> const&, mozilla::hal::ProcessPriority, mozilla::dom::ContentParent*, bool)]

layout/printing/crashtests/793844.html
pretty consistently either asserts or crashes
application crashed [@ mozilla::ProfilerParent::CreateForProcess(int)]
[Child 2666, Main Thread] ###!!! ASSERTION: Wrong Document Channel: 'request == mDocumentRequest', file /builds/worker/workspace/build/src/uriloader/base/nsDocLoader.cpp, line 1500
[Child 2666, Main Thread] ###!!! ASSERTION: Overwriting an existing document channel!: '(loadFlags & nsIChannel::LOAD_REPLACE) || !(mDocumentRequest.get())', file /builds/worker/workspace/build/src/uriloader/base/nsDocLoader.cpp, line 428

Thanks, Timothy! Fixing reproducible crashtest crashes will be a high priority for our Fission Nightly milestone (M6). I will file new blocking bugs for each of the test crashes you listed.

Blocks: 1601782
Fission Milestone: --- → M6
Depends on: 1614211, 1617315, 1580230
Priority: -- → P2
Depends on: 1620674
Depends on: 1620675
Depends on: 1620676
Depends on: 1620677
Depends on: 1620679
Alias: fission-crashtests
Depends on: 1585496
Depends on: 1614346
Whiteboard: fission-tests

Tracking for Fission Nightly M6a. We need to enable Fission crashtests (as tier 1) soon.

Fission Milestone: M6 → M6a
Summary: [meta] Fix crashtest fission failures → [meta] Fix crashtest fission failures and enable crashtests as tier 1

(In reply to Chris Peterson [:cpeterson] from comment #3)

We need to enable Fission crashtests (as tier 1) soon.

Enabling Fission crashtests is bug 1601782.

Summary: [meta] Fix crashtest fission failures and enable crashtests as tier 1 → [meta] Fix crashtest fission failures

And tests are enabled now in bug 1601782!

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