Closed Bug 1720573 Opened 3 years ago Closed 2 years ago

Font crashes with CJK characters: "assertion failed: self.font_contexts.lock_shared_context().has_font(&font.font_key)" and "adding native font failed"

Categories

(Core :: Graphics: Text, defect, P3)

Firefox 91
x86
Linux
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox-esr78 --- unaffected
firefox-esr91 --- affected
firefox92 --- wontfix
firefox93 --- wontfix
firefox94 --- wontfix
firefox95 --- wontfix
firefox96 --- wontfix

People

(Reporter: raycy.jp, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: correctness, crash, regression)

Crash Data

Attachments

(21 files)

(deleted), image/png
Details
(deleted), image/png
Details
(deleted), image/png
Details
(deleted), image/png
Details
(deleted), image/png
Details
(deleted), image/png
Details
(deleted), text/plain
Details
(deleted), text/plain
Details
(deleted), text/plain
Details
(deleted), text/plain
Details
(deleted), text/plain
Details
(deleted), text/plain
Details
(deleted), image/png
Details
(deleted), text/plain
Details
(deleted), image/png
Details
(deleted), image/png
Details
(deleted), text/plain
Details
(deleted), text/plain
Details
(deleted), text/plain
Details
(deleted), text/plain
Details
(deleted), text/plain
Details
Attached image Screenshot at 2021-07-15 05-57-29.png (deleted) —

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:89.0) Gecko/20100101 Firefox/89.0

Steps to reproduce:

Searching https://www.google.com/search?q=%E4%B8%80%E4%BA%BA%E3%81%82%E3%81%9F%E3%82%8A%E7%B4%94%E5%88%A9%E7%9B%8A ,
with some popups open by add-on:Popup window.

Actual results:

The result displaying of the search show with lack of most texts.
But can take a complete result of Screenshot.

Expected results:

The result displaying should show a complete result without any lack of texts.

The Bugbug bot thinks this bug should belong to the 'Firefox::Screenshots' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → Screenshots

(In reply to Release mgmt bot [:sylvestre / :calixte / :marco for bugbug] from comment #3)

The Bugbug bot thinks this bug should belong to the 'Firefox::Screenshots' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

I don't think so. The 'Firefox::Screenshots' component works fine, but the displaying of firefox:main is broken or lacking.

So, it seems that the graphic memory has the complete data, but the displaying process of firefox:main doesn't take the memory's data completely.

Means, the Firefox:core:displaying process taking out the graphic memory data incompletely..

There could be some relations with Tabbed browser.. Cause, opening mainwindow with some other child window by add-on:Popup window or from main to make child window to retweet

(In reply to raycy.jp from comment #5)

There could be some relations with Tabbed browser.. Cause, opening mainwindow with some other child window by add-on:Popup window or from main to make child window to retweet
it happens.

Component: Screenshots → Untriaged

There are two kind of pngs attached, one is taken by the component, the others are taken by app from outside from firefox.

"Screenshot at" s are by app from outside.
"Screenshot 2021 …” is taken by the component.

(In reply to Release mgmt bot [:sylvestre / :calixte / :marco for bugbug] from comment #3)

The Bugbug bot thinks this bug should belong to the 'Firefox::Screenshots' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Hi,

Could you please answer the following questions in order to further investigate this issue?

1- Does this issue happen with a new profile? Here is a link on how to create a new profile: https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles
2- Are you using add-ons? If so could you please list them? (you can try the issue while in Safe Mode. You can find helpful info here : https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode .)
3- Does this issue occur in the latest nightly version of firefox? Here is a link from where you can download it: https://www.mozilla.org/en-US/firefox/channel/desktop/

Thanks for the report.
Clara

Flags: needinfo?(raycy.jp)

The trouble could be concerning to the gtk, the Bugbug bot thinks. Could be...
https://bugzilla.mozilla.org/show_bug.cgi?id=1722426#c3

Flags: needinfo?(raycy.jp)

Hi , were you able to see my above comment?
Thanks!
Clara

Flags: needinfo?(raycy.jp)

Hi,

I'm marking this as Resolved-Incomplete due to lack of response. If the issue is still reproducible with the latest Firefox version, feel free to reopen the bug with more information.

Regards, Clara.

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE

(In reply to Clara Guerrero from comment #12)

Hi,

I'm marking this as Resolved-Incomplete due to lack of response. If the issue is still reproducible with the latest Firefox version, feel free to reopen the bug with more information.

Regards, Clara.

Hi,
I've set the font on firefox from linux mint default:Takao to Noto . and monitoring so far..
https://bugzilla.mozilla.org/show_bug.cgi?id=1722426#c12
The trouble looks calming ..
It seems being known that the Takao font sometimes makes garbled characters on firefox...
It might be this kind of thing...
Thanks.

Flags: needinfo?(raycy.jp)

The following report is just after the crash.
https://crash-stats.mozilla.org/report/index/ec4b6b9b-46bc-4211-86d0-a42da0210831

Just before above happening, garbled characters had happen,

and linux mint mate-screenshot --interactive captures only garbled charactered display,

but firefox component "Firefox Screenshots" takes picture as the characters as it should be...

https://twitter.com/raycy/status/1432743855758077952
https://twitter.com/raycy/status/1432746028147437573

Status: RESOLVED → UNCONFIRMED
Resolution: INCOMPLETE → ---
Summary: Lack of displaying most of texts happen, though can take complete Screenshot, later soon crashed. → Lack of displaying most of texts or gambled happen, though can take complete Screenshot by component, later soon crashed.
Version: Firefox 89 → Firefox 91
Summary: Lack of displaying most of texts or gambled happen, though can take complete Screenshot by component, later soon crashed. → Lack of displaying most of texts or garbled happen, though can take complete Screenshot by component, later soon crashed.

1729779 is concerning to webrender. In my case, webrender settings is false.

At the next picture, I'll show how complitely the component:"Take screenshot" take the picture,
instead of the glitching showings of the display...
Later on, crashed.
Relating reports supposed to be...
Report ID Date Submitted
bp-42e89a47-07af-43a4-8b33-84d1a0210910 9/11/21, 07:03 JST
bp-e9bee8ea-d710-4a7c-8ffc-486b80210910 9/11/21, 06:44 Jst

The complete screenshot by the firefox component, despite the glitching or garbled characters on the display shown.

Crash Signature: [@ libxul.so@0x6650f80 | libxul.so@0x9b69fff | libxul.so@0x9b69fff | libxul.so@0x4eb06cc | TakaoPGothic.ttf@0x1092572 ] [@ libxul.so@0x66bf830 | libxul.so@0x9c0bfff | libxul.so@0x9c0bfff | libxul.so@0x4f1830c | TakaoPGothic.ttf@0x599464 ] [@ libxul.so@0…
OS: Unspecified → Linux
Hardware: Unspecified → x86
Summary: Lack of displaying most of texts or garbled happen, though can take complete Screenshot by component, later soon crashed. → Japanese characters: Lack of displaying most of texts or garbled happen, though can take complete Screenshot by component, later soon crashed.

I'm seeking for avoiding to crash, the better settings,
now, the font settings for Japanese, Droid sans fallback and monospace.

Other conditions
☑ Allow pages to choose their own fonts, instead of your selections above
webrender false

recent crashes got, related or not...
Report ID Date Submitted JST
bp-2b76c80c-d212-493c-a60b-a7ae50210911 9/11/21, 13:26
bp-daf72c37-69c5-4104-ad66-b0aad0210911 9/11/21, 09:16
bp-49f61159-1637-4c54-9c01-6b04e0210910 9/11/21, 08:07
bp-42e89a47-07af-43a4-8b33-84d1a0210910 9/11/21, 07:03
bp-e9bee8ea-d710-4a7c-8ffc-486b80210910 9/11/21, 06:44

Summary: Japanese characters: Lack of displaying most of texts or garbled happen, though can take complete Screenshot by component, later soon crashed. → Japanese characters: Lack of displaying most of texts or garbled happen, though can take complete Screenshot by component, later soon crashed. Webrender settings, false.

Installed nightly, On nightly, Name Firefox
Version 93.0a1
Build ID 20210812124413
font setting default Japanese Takaos, checking "Allow ...".

At first, webrender:false, while browsing https://www.itsmarttricks.com/how-to-install-mozilla-firefox-nightly-browser-in-ubuntu-19-04/, glitches had happen. Soon, it recovered by itself.
Then, wbrender:true, and soon, crashed.

Restarting, changing settings of wbrender from true to false... or so...

While above, the left texts on the terminal.

I don't know how to enable "about:crashes" on the nightly... so...

(re-up, cause the last one had lost the last section)
Installed nightly, Name Firefox
Version 93.0a1
Build ID 20210812124413
font settings default: Japanese Takaos, checking "Allow ...".

At first, webrender:false, while browsing https://www.itsmarttricks.com/how-to-install-mozilla-firefox-nightly-browser-in-ubuntu-19-04/, glitches had happen. Soon, it recovered by itself.
Then, wbrender:true, and soon, crashed.

Restarting, changing settings of wbrender from true to false... or so...

While above, the left texts on the terminal.

I don't know how to enable "about:crashes" on the nightly... so...

Component: Untriaged → Graphics: Text
Product: Firefox → Core

The crash report in comment 14 shows "assertion failed: self.font_contexts.lock_shared_context().has_font(&font.font_key)", which sounds like webrender failed to receive or register an expected font resource. We've seen a few reports that seem quite similar, IIRC; Lee may remember more about these.

Flags: needinfo?(lsalzman)

The terminal console of followings above, containing most of duplicated parts and another one hour's.

Attached file No audio sound. (deleted) —

While no audio sound with some videos on going.

Nightly, Name Firefox Version 93.0a1 Build ID 20210812124413
font settings might be not default, changed to Droids and monospace , checking "Allow ...", and webrender, false.

As I wrote, I tryed webrender true, and crashed soon... while opening tabs like https://ctext.org/font-test-page/zh (or https://www.itsmarttricks.com/how-to-install-mozilla-firefox-nightly-browser-in-ubuntu-19-04/).

Later and now, Webrender, false. But got crash
(The other site, firefox often getting crashes while browsing is
http://www.nhc.gov.cn/xcs/yqtb/list_gzbd.shtml and its sub-links...
2021/09/13(Mon) 01:19:24 Tabtter
https://twitter.com/raycy/status/1437088464818749443
”“
The other procedures to make firefox crash are,
while browsing the site of some page like https://twilog.org/raycy/search?word=%E7%9C%8C%E5%A4%96&ao=a and click on the retweet icon: 🔃 ...,
another,
while browsing the site of some page like https://www.fileformat.info/info/unicode/char/search.htm?q=arrow&preview=entity and scroll downwards...
2021/09/13(Mon) 12:30:25 Tabtter
https://twitter.com/raycy/status/1437257333164285957

(In reply to raycy.jp from comment #25)
Not always but sometimes...

Attachment #9240949 - Attachment mime type: application/octet-stream → text/plain
Attachment #9240948 - Attachment mime type: application/octet-stream → text/plain
Attachment #9240809 - Attachment mime type: application/octet-stream → text/plain

(In reply to raycy.jp from comment #25)
I'm not sure now, at what time I've changed the font settings from default(Takaos) to Droids and monospace...

Might be after got crash on the settings of "webrender: false", and "font default(Takaos)"...

Now, the font settings for Japanese etc. are Droids and monospace , checking "Allow ...", and "webrender, false".

The terminal console, until crash. Just before crash, I clicked some add-on icons and they showed a blank menu pop-up each time... and soon later, crashed.

firefox nighly launched from terminal and typing firefox-trunk,
can't find about:crashes and bug-reporter seems doesn't work...

How much RAM do you have installed, and how much is available for applications to use? The information from something like "top" would be helpful here...

Flags: needinfo?(lsalzman) → needinfo?(raycy.jp)
Flags: needinfo?(raycy.jp)
Attached image Screenshot at 2021-09-14 06-30-24.png (deleted) —

A child window for file upload shows blank, and while on console https://bugzilla.mozilla.org/attachment.cgi?id=9241010 .

(In reply to Lee Salzman [:lsalzman] from comment #30)

How much RAM do you have installed, and how much is available for applications to use? The information from something like "top" would be helpful here...

Once, my RAM and swap meter was close to full or almost full. But now, after "swapoff -a && swapon -a", https://twitter.com/raycy/status/1436977603483627526
it's much better, later on...

Changing severity to S3. It's reproducible for the reporter, but not yet for Mozilla engineers; no related crash signatures yet.

Severity: -- → S3
Priority: -- → P3

without add-ons , didn't crash so far... , on another profile, I'm testing.

got crash.

Summary: Japanese characters: Lack of displaying most of texts or garbled happen, though can take complete Screenshot by component, later soon crashed. Webrender settings, false. → Font crashes with CJK characters: "assertion failed: self.font_contexts.lock_shared_context().has_font(&font.font_key)" and "adding native font failed"
Blocks: wr-oom
Crash Signature: libxul.so@0x66bf830 | libxul.so@0x9c0bfff | libxul.so@0x9c0bfff | libxul.so@0x4f1830c | TakaoPMincho.ttf@0x447f68 ] → libxul.so@0x66bf830 | libxul.so@0x9c0bfff | libxul.so@0x9c0bfff | libxul.so@0x4f1830c | TakaoPMincho.ttf@0x447f68 ] [@ libxul.so@0x628cbd0 | libxul.so@0x99a9fff | libxul.so@0x99a9fff | libxul.so@0x3e5932b | libxul.so@0x6a64213 | NotoSansCJK-Bold.ttc@0x50…

(In reply to raycy.jp from bug 1737810 comment #50)

Another one comes...
"Firefox 96.0a1 Crash Report [@ <webrender::platform::unix::font::FontContext as webrender::glyph_rasterizer::AddFont>::add_font ]
nightly 96.0a1
OS Arch Linux

MOZ_CRASH Reason (Sanitized)
adding native font failed: file=/usr/share/fonts/noto/NotoSans-Regular.ttf, err=Os { code: 2, kind: NotFound, message: "No such file or directory" }"
https://crash-stats.mozilla.org/report/index/d15fc6fc-e026-4aa9-9454-29e1d0211127

I saw font crashes when I run out of file descriptors.
Please post the output of the following commands when this crash crash occurs or when you think it might occur shortly after:

(Gian-Carlo Pascutto [:gcp] from bug 1739924 comment #18)

Interesting output to check when this problem is happening:

ulimit -a -H
ulimit -a
pgrep -f firefox | xargs -I {} bash -c 'printf {}" "; lsof -p {} | wc -l'
pgrep -f firefox | xargs -I {} bash -c 'printf {}" "; pmap -p {} | wc -l'

Crash Signature: libxul.so@0x66bf830 | libxul.so@0x9c0bfff | libxul.so@0x9c0bfff | libxul.so@0x4f1830c | TakaoPMincho.ttf@0x447f68 ] [@ libxul.so@0x628cbd0 | libxul.so@0x99a9fff | libxul.so@0x99a9fff | libxul.so@0x3e5932b | libxul.so@0x6a64213 | NotoSansCJK-Bold.ttc@0x50… → libxul.so@0x66bf830 | libxul.so@0x9c0bfff | libxul.so@0x9c0bfff | libxul.so@0x4f1830c | TakaoPMincho.ttf@0x447f68 ] [@ libxul.so@0x628cbd0 | libxul.so@0x99a9fff | libxul.so@0x99a9fff | libxul.so@0x3e5932b | libxul.so@0x6a64213 | NotoSansCJK-Bold.ttc@0x5…

(Darkspirit from bug 1737810 comment #40)

(raycy.jp from comment #31)

bp-cd8bf1dc-a048-4838-9842-7c0c30211119

This is a report from Nightly, but there is no Snap Nightly, that's why I removed this bug from the snap meta bug.

(Jonathan Kew (:jfkthame) from bug 1737810 comment 41)

That looks like it may actually be an OOM (see the GraphicsCriticalError annotation).

I wonder if this is actually FreeType encountering an OOM situation (maybe remaining memory is too fragmented for the big font file) while trying to read the font, but returning Unknown_File_Format rather than Out_Of_Memory? I see a similar "wr_renderer_render: OutOfMemory" annotation in some of the other reports, too, though by no means all of them.

bug 1729779 is in see See Also.

(In reply to Darkspirit from comment #42)

Interesting output to check when this problem is happening:

ulimit -a -H
ulimit -a
pgrep -f firefox | xargs -I {} bash -c 'printf {}" "; lsof -p {} | wc -l'
pgrep -f firefox | xargs -I {} bash -c 'printf {}" "; pmap -p {} | wc -l'

another crash
”nightly Version 96.0a1
OS Linux Mint 19.3 Tricia
MOZ_CRASH Reason (Sanitized)
adding native font failed: file=/usr/share/fonts/opentype/noto/NotoSansCJK-Regular.ttc err=2"
bp-4465a0b6-0d86-424d-9fa8-aca420211129

~$ pgrep -f firefox | xargs -I {} bash -c 'printf {}" "; pmap -p {} | wc -l'
24756 2121
25116 353
25239 668
25266 626
25300 917
25340 993
25445 835
25475 484

(In reply to Darkspirit from comment #42)

Whether is it related with https://bugzilla.mozilla.org/show_bug.cgi?id=1737810#c53 or not,

I've changed about:config, dom.storage.snapshot_reusing "false" to "true"

So far, no crashes, only two times at the risk though...
I'm monitoring beyond now...

Whether is it related with https://bugzilla.mozilla.org/show_bug.cgi?id=1737810#c53 or not,

I've changed about:config, dom.storage.snapshot_reusing "true" to "false" <- correction.

So far, no crashes, only two times at the risk though...
I'm monitoring beyond now...

Attached file getting another not well condition... (deleted) —

seems going to crash...

Can you try setting the pref gfx.webrender.multithreading to false? That might use less font threads and as such less memory loading the font into each thread, hopefully forestalling any OOMing.

Flags: needinfo?(raycy.jp)

(In reply to Lee Salzman [:lsalzman] from comment #51)

"setting the pref gfx.webrender.multithreading to false" seems to lessen crashes, but not completely.

bp-16e41b64-2a96-4487-b2ed-cf9d20211201

raycy@raycy-2010:$ ulimit -a -H
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 29634
max locked memory (kbytes, -l) 65536
max memory size (kbytes, -m) unlimited
open files (-n) 1048576
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) unlimited
cpu time (seconds, -t) unlimited
max user processes (-u) 29634
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
raycy@raycy-2010:
$ ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 29634
max locked memory (kbytes, -l) 65536
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 29634
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
raycy@raycy-2010:$ pgrep -f firefox | xargs -I {} bash -c 'printf {}" "; lsof -p {} | wc -l'
15451 lsof: WARNING: can't stat() tracefs file system /sys/kernel/debug/tracing
Output information may be incomplete.
lsof: WARNING: can't stat() ext4 file system /media/root/9442f513-c86b-692b-642f-9b6394583785
Output information may be incomplete.
^[[A281
raycy@raycy-2010:
$ pgrep -f firefox | xargs -I {} bash -c 'printf {}" "; pmap -p {} | wc -l'
15451 403
raycy@raycy-2010:~$

Flags: needinfo?(raycy.jp)

Just after another crash bp-cef745ac-07b1-4edf-ab7d-f53510211201 ,

raycy@raycy-2010:~$ ulimit -a -H
core file size          (blocks, -c) unlimited
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 29634
max locked memory       (kbytes, -l) 65536
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1048576
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) unlimited
cpu time               (seconds, -t) unlimited
max user processes              (-u) 29634
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited
raycy@raycy-2010:~$ ulimit -a
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 29634
max locked memory       (kbytes, -l) 65536
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 29634
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited
raycy@raycy-2010:~$ pgrep -f firefox | xargs -I {} bash -c 'printf {}" "; lsof -p {} | wc -l'
17106 lsof: WARNING: can't stat() tracefs file system /sys/kernel/debug/tracing
      Output information may be incomplete.
lsof: WARNING: can't stat() ext4 file system /media/root/9442f513-c86b-692b-642f-9b6394583785
      Output information may be incomplete.
378
raycy@raycy-2010:~$ pgrep -f firefox | xargs -I {} bash -c 'printf {}" "; pmap -p {} | wc -l'
17106 403
raycy@raycy-2010:~$ 

Thanks for the terminal output, it is not required anymore.

https://crash-stats.mozilla.org/report/index/44956c0c-2a34-4363-897b-5ff050211217
Slackware Linux
MOZ_CRASH Reason (Sanitized)
adding native font failed: file=/usr/share/fonts/TTF/wqy-zenhei.ttc err=2

https://crash-stats.mozilla.org/report/index/9b6ee06e-9e42-4ab4-a668-969320211216
Ubuntu 18.04.5 LTS
MOZ_CRASH Reason (Sanitized)
adding native font failed: file=/usr/share/fonts/opentype/noto/NotoSansCJK-Regular.ttc err=2

messages with err=2
1de8a5f8-4fc7-4ffb-bd65-e69c30211220
7e2223d7-930b-4f8e-ad0c-13bed0211219
a1ca5105-dac4-41b0-b3f3-502b80211219
a5de7e49-7cab-474b-9471-4b1550211218
97231273-7c1f-4be9-8924-54a0f0211218
44956c0c-2a34-4363-897b-5ff050211217
9b6ee06e-9e42-4ab4-a668-969320211216
c162e58c-0422-47f2-8b17-f6e9b0211219

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

Status: UNCONFIRMED → NEW
Ever confirmed: true

The severity field for this bug is relatively low, S3. However, the bug has 3 duplicates.
:lsalzman, could you consider increasing the bug severity?

For more information, please visit auto_nag documentation.

Flags: needinfo?(lsalzman)
Flags: needinfo?(lsalzman)
Crash Signature: NotoSerifCJK-Regular.ttc@0x36b8053] [@ libxul.so@0x6650f80 | libxul.so@0x9b69fff | libxul.so@0x9b69fff | libxul.so@0x4eb06cc | NotoSerifCJK-SemiBold.ttc@0x887053] → NotoSerifCJK-Regular.ttc@0x36b8053] [@ libxul.so@0x6650f80 | libxul.so@0x9b69fff | libxul.so@0x9b69fff | libxul.so@0x4eb06cc | NotoSerifCJK-SemiBold.ttc@0x887053] [@ libxul.so@0x6758920 | libxul.so@0xa071fff | libxul.so@0xa071fff | libxul.so@0x41cbc8b |…

raycy, does this still crash for you when using a newer current version?

(according to the currently documented signatures, the crash rate has signficantly dropped)

Crash Signature: NotoSerifCJK-Regular.ttc@0x36b8053] [@ libxul.so@0x6650f80 | libxul.so@0x9b69fff | libxul.so@0x9b69fff | libxul.so@0x4eb06cc | NotoSerifCJK-SemiBold.ttc@0x887053] [@ libxul.so@0x6758920 | libxul.so@0xa071fff | libxul.so@0xa071fff | libxul.so@0x41cbc8b → NotoSerifCJK-Regular.ttc@0x36b8053] [@ libxul.so@0x6650f80 | libxul.so@0x9b69fff | libxul.so@0x9b69fff | libxul.so@0x4eb06cc | NotoSerifCJK-SemiBold.ttc@0x887053] [@ libxul.so@0x6758920 | libxul.so@0xa071fff | libxul.so@0xa071fff | libxul.so@0x41cbc8b
Flags: needinfo?(raycy.jp)

Redirect a needinfo that is pending on an inactive user to the triage owner.
:lsalzman, since the bug has recent activity, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(raycy.jp) → needinfo?(lsalzman)
Flags: needinfo?(lsalzman)

Closing because no crashes reported for 12 weeks.

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

Attachment

General

Creator:
Created:
Updated:
Size: