Open Bug 2034985 Opened 3 days ago Updated 1 day ago

print (save to PDF) makes Firefox 150.0 crash

Categories

(Core :: Printing: Output, defect)

Firefox 150
defect

Tracking

()

UNCONFIRMED

People

(Reporter: vincent-moz, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:150.0) Gecko/20100101 Firefox/150.0

Steps to reproduce:

  1. Open any web page.
  2. Choose File → Print… (or via a print button from the web page, when available).
  3. Click on "Save" (note: in my case, the only possible destination is "Save to PDF").

Actual results:

Firefox crashed. A dialog opened with: "The application failed to generate crash information." (perhaps because I run Firefox in firejail, but in any case, this message is meaningless as one doesn't know why it failed exactly), proposing to restart Firefox.

Note that when this occurred initially, this was an important generated page (an e-ticket), and it was not restored! Fortunately, I could retrieve the e-ticket in another way.

Expected results:

The file chooser should have been opened.

With Firefox 149 and before, I have never had such a crash.

Note: This seems 100% reproducible. After downgrading to FF 149.0.2 (using the same profile), I no longer get these crashes.

Nightly 152.0a1 (2026-04-25), run in a private firejail directory, does not crash.

The Bugbug bot thinks this bug should belong to the 'Core::Printing: Output' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Printing: Output
Product: Firefox → Core

Can you go to about:crashes and share some crash IDs?

Flags: needinfo?(vincent-moz)

The latest crash ID was on 2025-04-12. So it seems that crash information was not recorded, which would be consistent with the "The application failed to generate crash information." message.

But the crash no longer occurs.

Flags: needinfo?(vincent-moz)

BTW, the print directory was reset to my home directory instead of getting the usual one.

You need to log in before you can comment on or make changes to this bug.