Closed Bug 1749696 Opened 3 years ago Closed 2 years ago

Crash in [@ mozilla::dom::AutoJSAPI::Init | nsQueryJSActor::operator() ]

Categories

(Core :: DOM: Navigation, defect, P3)

Firefox 96
ARM64
macOS
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: fzczx123, Unassigned)

References

Details

(Whiteboard: [QA-not-actionable])

Crash Data

Maybe Fission related. (DOMFissionEnabled=1)

Crash report: https://crash-stats.mozilla.org/report/index/bf4c1390-61f2-44de-830e-a73910220112

Reason: EXC_BAD_ACCESS / KERN_INVALID_ADDRESS

Top 10 frames of crashing thread:

0 XUL mozilla::dom::AutoJSAPI::Init dom/script/ScriptSettings.cpp:437
1 XUL nsQueryJSActor::operator const dom/ipc/jsactor/nsQueryActor.h:37
2 XUL nsCOMPtr_base::assign_from_helper xpcom/base/nsCOMPtr.cpp:109
3 XUL nsWindowRoot::GetControllerForCommand dom/base/nsWindowRoot.cpp:226
4 XUL mozilla::EventStateManager::DoContentCommandEvent dom/events/EventStateManager.cpp:5977
5 XUL mozilla::EventStateManager::PreHandleEvent dom/events/EventStateManager.cpp:920
6 XUL mozilla::PresShell::EventHandler::DispatchEvent layout/base/PresShell.cpp:8247
7 XUL mozilla::PresShell::EventHandler::HandleEventWithCurrentEventInfo layout/base/PresShell.cpp:8216
8 XUL mozilla::PresShell::EventHandler::HandleEventWithFrameForPresShell layout/base/PresShell.cpp:8049
9 XUL mozilla::PresShell::HandleEvent layout/base/PresShell.cpp:6880
Component: Untriaged → Layout
Product: Firefox → Core
Whiteboard: [QA-not-actionable]

This bug can be triggered a lot more frequently if I navigate back and forth a lot via right clicking the "go back" or "go forward" button.

The severity field is not set for this bug.
:jwatt, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(jwatt)

This is also a Fission event handling issue. Moving into DOM:Events. CCing Edgar.

Component: Layout → DOM: Events
Flags: needinfo?(jwatt)

Not sure about component, but not DOM: Events. Something going wrong in controller actor handling.

Component: DOM: Events → DOM: Navigation
Severity: -- → S3
Priority: -- → P3

The bug has a crash signature, thus the bug will be considered confirmed.

Status: UNCONFIRMED → NEW
Ever confirmed: true

Also this signature is really generic and should be added to the prefix list.

Depends on: 1774110
See Also: → 1774111
Crash Signature: [@ mozilla::dom::AutoJSAPI::Init] → [@ mozilla::dom::AutoJSAPI::Init] [@ mozilla::dom::AutoJSAPI::Init | nsQueryJSActor::operator() ]
Summary: Crash in [@ mozilla::dom::AutoJSAPI::Init] → Crash in [@ mozilla::dom::AutoJSAPI::Init | nsQueryJSActor::operator() ]
Severity: S3 → N/A

On macOS, we use:

The others are not used in macOS except synthesizing it with nsIDOMWindowUtils.

On Windows, we use eContentCommandCopy, eContentCommandCut, eContentCommandPaste, eContentCommandUndo, eContentCommandRedo when they are called via native message of Win32 API or user uses multimedia keyboard or mouse which has corresponding key/button.

Olli, did you change severity from S3 to N/A accidentally?

Flags: needinfo?(smaug)

Hmm, I think so.

Severity: N/A → S3
Flags: needinfo?(smaug)

Closing because no crashes reported for 12 weeks.

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