1591705 - Firefox crashes when visiting businessinsider page

Status: RESOLVED DUPLICATE of bug 1581138

(Core :: DOM: Navigation, defect)

Description

[Asif Youssuff]

Not sure what prefs are causing this, but the issue is reproducible.

I visit https://www.businessinsider.com/fitness-experts-sit-ups-worthless-what-to-do-instead-2018-7 and Firefox quits, closing all windows and displaying the crash reporter.

15:23.14 INFO: No more inbound revisions, bisection finished.
15:23.14 INFO: Last good revision: f748a3d2cdf108e9443fd15332efe477c7c398a9
15:23.14 INFO: First bad revision: 25b533bff4051e6a8177bbc83eed49ac460e109e
15:23.14 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=f748a3d2cdf108e9443fd15332efe477c7c398a9&tochange=25b533bff4051e6a8177bbc83eed49ac460e109e

Comment 1

[Asif Youssuff]

Attachment: about:support

Comment 2

[Mark Banner (:standard8)]

Getting example crash ids from about:crashes might also be useful

Comment 3

[Matt Woodrow (:mattwoodrow)]

This doesn't reproduce for me. Can you please post a crash id from about:crashes?

Comment 4

[Asif Youssuff]

It doesn't seem to be crashing for me anymore in the latest Nightly, and it is hard to identify a good crash report because as soon as Firefox crashes, it creates at least 8 or so reports (because this crash crashes the entire browser).

These may help, I don't know:

Report ID
bp-890f197d-667d-4d56-aaa1-600a50191029
bp-eadef5ba-d203-4cc1-88f7-98de30191029
bp-d89543c6-a259-4b3f-a768-8c9900191029
bp-88c57eff-6045-471d-ade7-f55360191029
bp-bdaa9f12-4e56-4156-b319-dff830191029
bp-605236db-3560-42f7-9f45-2932f0191029
bp-43c79174-1394-4349-8377-838690191029
bp-5dffdf47-5bf8-4148-abfb-8b22f0191029
bp-c5b93b15-107b-4b54-bf6d-c6feb0191029
bp-4c234f14-74b3-476a-b228-4731e0191029
bp-18961e6b-a96e-4604-860f-683bc0191029
bp-2105db6f-e4b3-45cc-8f21-68e900191029
bp-1914b967-1f02-4777-8df0-13c2a0191029
bp-75865b4c-4232-4591-9b98-2d0a90191029
bp-87e85d53-6948-48ec-9482-bcb6f0191029
bp-cf81da06-0566-4863-894a-ec6330191029
bp-a7018225-e8ae-4420-9934-156500191029
bp-70f4eb7c-3a5f-4a09-bad0-8fedb0191029
bp-f54d1c83-6afa-4a3a-b1cf-6f3e50191029
bp-58284a52-0e9a-4da8-bca0-e92770191029
bp-574e850c-f372-405f-871f-2aa6e0191029
bp-b1a3639a-b4c1-497a-8aab-0716a0191029
bp-34808157-08af-40e5-bc08-cd7c90191029
bp-63ae0191-a240-42c4-9da0-8753d0191029
bp-953cec02-887b-426e-be91-b4c0d0191029
bp-ff94e85e-d7c0-4e12-90c1-34f9e0191029
bp-0c042cb3-2da4-4e26-a832-8b90a0191029
bp-7019c78c-99fd-4d74-992b-da6c50191029
bp-31e23ef3-41ed-4517-90ba-5bef80191029
bp-0d36ff8d-4285-4b8d-920b-3bed70191029
bp-c90604f2-080a-433a-ae96-8a3e90191029
bp-68c2b9a1-86a3-48b9-9b9e-72f800191029
bp-82694447-7d8e-4d85-b719-124a30191029
bp-37e9e52a-7f78-47b1-a446-9ebd70191029
bp-4fa088c9-319a-4963-947a-ab0430191029
bp-e7733881-9938-454d-905c-41f640191029
bp-1441ef06-b98b-4d2a-a7a3-a17f60191029
bp-8172f92f-7ed7-4aa1-bdd2-18ca50191029
bp-b9896801-5a89-440b-a84a-d10470191029
bp-a163e2c4-acec-4e9e-b62a-b2f360191029
bp-611b1ed2-1e61-426e-9bc8-840090191029
bp-a5a4e0ef-48cb-47c7-b7f4-1a21a0191029
bp-19692100-ff9f-4f28-80c7-7c6b80191029
bp-4295df7b-79ff-4c4f-a783-a0e200191029
bp-cea4afff-62a4-45ce-b51a-58fee0191029
bp-40ecde89-f769-4b07-bf08-b4f9f0191029
bp-f2d6caf1-f47c-47ff-8748-d9cb30191029

Comment 5

[Jean-Yves Avenard [:jya]]

Going to mark it as WFM as per comment 4. Please re-open if it happens again.

Comment 6

[Asif Youssuff]

Just tried this again this morning with the latest nightly.

Tried it after clearing out my session using a backup of the profile I took after reporting this issue initially, and I think I got a better crash report:

bp-69817a93-890a-46db-b345-c8b580191029

Saw this in the terminal I had opened this in:

ExceptionHandler::GenerateDump cloned child 18674
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.

Comment 7

[Dragana Damjanovic [:dragana]]

This looks like a crach of the parent process.
I would like to ask someone who knows IPC to take a look.

Comment 8

[Jed Davis [:jld] ⟨⏰|UTC-7⟩ ⟦he/him⟧]

BrowsingContext → DOM.

Comment 9

[Jim Mathies [:jimm]]

Looks fission related.

Comment 10

[Andrew McCreight [:mccr8]]

The crash is in mozilla::dom::BrowsingContext::IPCInitializer::GetParent(), and the crash reason is MOZ_RELEASE_ASSERT(parent). Looks like a dupe of bug 1581138.