Regression: Some PDF text renders as blank in Firefox 155+, workround by setting pdfjs.disableFontFace=true
Categories
(Core :: Graphics: Canvas2D, defect)
Tracking
()
People
(Reporter: Coelacanthus, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
|
1.70 MB,
image/png
|
Details |
Steps to reproduce:
- Open https://bugzilla.mozilla.org/attachment.cgi?id=9537141 (the example PDF of https://bugzilla.mozilla.org/show_bug.cgi?id=2009940, which has the same workaround. Althrough I can see the same issue in any PDF, but I use this one so I don't need to upload new file) in Firefox.
- Observe that some text shows as blank.
Actual results:
Body text renders as blank; unreadable. See
Expected results:
Text renders normally.
Additional information:
pdfjs.disableFontFace default is false; setting it to true fixes the rendering.
Use mozregression --arg='https://bug2009940.bmoattachments.org/attachment.cgi?id=9537141' --bad 2026-08-18 --good 2026-06-18 to find the bad commit.
8:01.46 INFO: Narrowed integration regression window from [5ab718c5, cc056d05] (3 builds) to [5ab718c5, c9c78ae9] (2 builds) (~1 steps left)
8:01.46 INFO: No more integration revisions, bisection finished.
8:01.46 INFO: Last good revision: 5ab718c5a32c093f8846931b1c2a9fcf92c37058
8:01.46 INFO: First bad revision: c9c78ae99215d977e1b6c17377637ae04f81275f
8:01.46 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=5ab718c5a32c093f8846931b1c2a9fcf92c37058&tochange=c9c78ae99215d977e1b6c17377637ae04f81275f
With mozregression I got the first bad revision is https://hg-edge.mozilla.org/integration/autoland/rev/c9c78ae99215d977e1b6c17377637ae04f81275f, I don't understand the relation (so I run mozregression twice to ensure I didn't misoperate), but I post here so experienced developers may know why.
Comment 1•3 months ago
|
||
FYI, when pdfjs.disableFontFace is true, pdf.js uses it's own font renderer (glyph paths are extracted from the font and drawn on the canvas).
:Jamie, could you have a look please ?
| Reporter | ||
Comment 2•3 months ago
|
||
- I met this issue on Arch Linux (with Firefox Nightly 156.0a1 (2026-08-17) and Firefox developer edition 155.0b1).
- My firiend can't reproduce this issue on both Firefox Nightly 156.0a1 (2026-08-18) (64-bit) and Firefox developer edition 155.0b1 on Windows 11.
- I have no macOS device so I can't test it on macOS.
- I also can't reproduce it on Firefox Nightly Android 156.0a1-20260818092026.
| Reporter | ||
Comment 3•3 months ago
|
||
I have another try today. Since the first bad revision only changed WebGL code, so I think it may be related to GPU drivers. So
- I try to downgrade or upgrade kernel version, but it doesn't take effect.
- I try to downgrade or upgrade Mesa (since it's OpenGL userspace driver). After upgrade from 26.2.0.r225111.379cc7b4a8f to 26.3.0.r228214.88be0c15190, the issue disappeared.
So the issue is the Mesa have some bug at 379cc7b4a8f, https://hg-edge.mozilla.org/integration/autoland/rev/c9c78ae99215d977e1b6c17377637ae04f81275f just introduce the code which will trigger the bug. So now this report can be marked upstream issue. Since it has been fixed in newer Mesa version and bisect it need 12 rounds and took long time to build, I decide not to bisect it to find the first bad Mesa or the fix commit.
Updated•1 month ago
|
Description
•