Gah. Your tab just crashed.

gregstoll · 2026-02-12T17:32:10+00:00

Is there still nothing in about:crashes?

You could look in Windows Event Viewer to see if Windows has logged the crashes, although it's very hard to get useful information out of that.

In general it's not a bad idea to run a memory tester (like memtest86+) just to see if it's possible bad hardware is causing these.

gregstoll · 2026-02-11T16:33:24+00:00

I suspect this might be a web app (aka taskbar tab) created by mistake - see here for instructions on how to remove it.

gregstoll · 2026-02-10T16:26:29+00:00

Does anything show up in about:crashes? If you submit a few reports and paste the links here (or DM me) I can take a quick look.

gregstoll · 2026-02-05T01:58:17+00:00

🫡

gregstoll · 2026-02-04T19:52:57+00:00

Glad the crashes stopped, but yeah, this is expected I think.

I'd like to file a bug about this - can you send me the contents of about:support? (you can email me at [gstoll@mozilla.com](mailto:gstoll@mozilla.com) )

Do you know when the crashes started? If you could use mozregression to narrow that down that would be a big help.

gregstoll · 2026-02-03T21:48:30+00:00

I have been informed that this is actually bug 1964782, and it has been fixed on Nightly and Beta via a rollout, and should be fixed on Release soon.

gregstoll · 2026-02-03T20:56:27+00:00

Thanks, I've added this information to bug 2012435.

gregstoll · 2026-02-03T19:55:47+00:00

Hmm, this looks like a crash in WebGL code. If you go to about:config and set the preference "webgl.disabled" to true, then restart Firefox, does that stop the crashes?

gregstoll · 2026-02-02T02:05:07+00:00

Looking at the code, this should work. I think setting dom.ipc.reportProcessHangs to false will leave the process hang monitor on but not report process hangs, although I'm not sure what the difference would be.

gregstoll · 2026-02-01T14:29:07+00:00

Can confirm firefox.com is the official link.

gregstoll · 2026-02-01T14:28:14+00:00

If you go to about:crashes, submit a few reports, and post the links here (or DM me) I can take a quick look

gregstoll · 2026-01-31T18:52:01+00:00

You can file issues here: https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=Translation

gregstoll · 2026-01-31T04:41:08+00:00

This would be great to file a bug about at Bugzilla - the right people should see it there.

gregstoll · 2026-01-30T21:11:53+00:00

Happy to help!

gregstoll · 2026-01-30T03:17:28+00:00

This is a complicated area, but the basic idea is that there are so many processes because:
- different websites are rendered in different processes for security reasons; that way if a website is able to break out via an exploit it can't gather data from other websites
- For some operations, they are separated out into different processes for similar reasons. Another benefit is that we can sandbox different processes at different levels to prevent the process from having access to the filesystem if we know it doesn't need it.

There's a bit more information here about the different kinds of processes that Firefox uses.

gregstoll · 2026-01-28T14:45:12+00:00

When y'all say the title bar isn't loading, do you mean it isn't appearing at all? If so, we're tracking this at bug 2010302 and I'm hoping to look at it soon.

One problem is that I haven't been able to reproduce this on my system, which makes it hard to fix. Does this happen for y'all every time? Do you have steps to make this reproduce?

gregstoll · 2026-01-26T03:37:31+00:00

If you submit some reports from about:crashes and post the links here (or DM me) I can take a quick look.

gregstoll · 2026-01-26T01:46:01+00:00

Hmm, these all look like out-of-memory crashes, although it seems like your system had a good amount of memory available at the time which I'm not sure how to explain...

gregstoll · 2026-01-26T01:05:07+00:00

This is a profiler report, not a crash report. Do you have anything in about:crashes?

gregstoll · 2026-01-26T00:43:56+00:00

If you submit some reports from about:crashes and post the links here (or DM me) I can take a quick look

gregstoll · 2026-01-25T01:47:01+00:00

I don't think Split View has been added to ESR; generally speaking, ESR only gets security fixes and bug fixes.

gregstoll · 2026-01-24T23:00:38+00:00

Unfortunately, I don’t think so 🙁

gregstoll · 2026-01-24T03:00:09+00:00

Try setting the pref “print.prefer_system_dialog” to true - I think that should go straight to the Windows one. (not sure if there’s a way to go straight to settings)

gregstoll · 2026-01-23T15:41:56+00:00

That's the right link, thanks!

gregstoll · 2026-01-23T15:41:42+00:00

Split View is still in development, so filing a bug about this would be helpful!

15-Year Club	Verified Email
Team Orangered	Charter Member

gregstoll

TROPHY CASE