New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 776718 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Dec 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: InitDefaultFont(). Could not find the default font in platform_font_linux.cc

Project Member Reported by ClusterFuzz, Oct 20 2017

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=4504570213695488

Fuzzer: jsbell_serviceworker
Job Type: linux_msan_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  InitDefaultFont(). Could not find the default font in platform_font_linux.cc
  gfx::PlatformFontLinux::PlatformFontLinux
  gfx::PlatformFont::CreateDefault
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=510349:510357

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4504570213695488

Additional requirements: Requires Gestures

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Cc: msrchandra@chromium.org pnangunoori@chromium.org
Labels: Test-Predator-Wrong
Owner: jonr...@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.
Using the code search for the file, “platform_font_linux.cc” assigning to concern owner from GIT blame.
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/393cc78cf982dacd721f3616b0afb752d42d9c77

@jonross -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thank You.

Cc: jonr...@chromium.org
Owner: pnangunoori@chromium.org
My change logs a fatal error of system resource files not being available.

This can be caused by:
  -font_loader service shutting down/crashing
  -overall shutdown of the browser triggering while trying to load fonts
  -files not being on the system

The first two would hopefully have crashes elsewhere in the logs. The later would require debugging the machine.

However this CHECK is just a symptom of the problem this clusterfuzz case has uncovered. It will need further triaging to find the root cause
Cc: mmoroz@chromium.org
mmoroz@ -- Could you please help in this for C#2.

Thanks in advance!

Comment 4 by mmoroz@chromium.org, Dec 21 2017

Cc: mbarbe...@chromium.org
I'm afraid we don't have a reliably way to reproduce this crash, since it's marked as non-reproducible. However, we see that crash happening quite often, this is why it got reported. Probably the best advice here would be to try landing a speculative fix based on the stacktrace, if possible. Then, after a couple of days, check Statistics section on ClusterFuzz report page: https://clusterfuzz.com/v2/testcase-detail/4504570213695488?noredirect=1

If the fix worked, total number of crashes should significantly drop.

CC'ing Marty in case there is anything else we can do.
Project Member

Comment 5 by ClusterFuzz, Dec 21 2017

ClusterFuzz has detected this issue as fixed in range 514495:514498.

Detailed report: https://clusterfuzz.com/testcase?key=4504570213695488

Fuzzer: jsbell_serviceworker
Job Type: linux_msan_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  InitDefaultFont(). Could not find the default font in platform_font_linux.cc
  gfx::PlatformFontLinux::PlatformFontLinux
  gfx::PlatformFont::CreateDefault
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=510349:510357
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=514495:514498

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4504570213695488

Additional requirements: Requires Gestures

See https://github.com/google/clusterfuzz-tools for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Project Member

Comment 6 by ClusterFuzz, Dec 21 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 4504570213695488 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

Sign in to add a comment