[Bug]: browser-wide crash

[mchmatt]

Describe the bug

Do not try this if you have important stuff open. This will crash all tabs and profiles, not just the one tab you're testing with.

Notes

This can be triggered programmatically by doing window.open("<url>", "_blank");

Expected behavior

No response

Screenshots/Recordings

No response

Steps to reproduce

1. Install MetaMask and set up a wallet
2. Open chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/notification.html or moz-extension://a0b28803-be23-4c3d-81d2-9735449f7d26/notification.html as a new tab

Error messages or log output

Detection stage

In production (default)

Version

12.10.1

Build type

None

Browser

Chrome, Firefox

Operating system

Windows, MacOS

Hardware wallet

No response

Additional context

No response

Severity

No response

[mchmatt]

Also happens in 12.10.1 (latest in Chrome store); having Notifications disabled or enabled doesn't seem to matter

[DanielTech21]

Hi @mchmatt
Thanks for reporting this to us.

It has been assigned to the relevant product team to investigate this further.

[dbrans]

This is a pretty annoying UX issue: if someone accidentally opens notification.html in a regular tab, it triggers a window-close behavior that can create a frustrating loop.

The tricky part is when Chrome is set to restore previous sessions – you can get stuck in a situation where the profile keeps closing itself because notification.html auto-closes the window.

I think this happens because notification.html is designed to close itself when there's nothing to confirm, but it shouldn't close the entire window when opened directly.

For anyone running into this: you can work around it by opening settings (CMD-,) and using "close other tabs" to break the loop.

Looping in @Gudahtt and @danjm for visibility

[dbrans]

Removing rollout-blocker since this is reproducible in 12.9.3.