New issue
Advanced search Search tips

Issue 866234 link

Starred by 2 users
Status: WontFix
Owner:
drott@chromium.org
Closed: Dec 14
Cc:
enne@chromium.org
e...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Stack-overflow in ComputeUserRequestedAlignmentLog

Project Member Reported by ClusterFuzz, Jul 21 
Detailed report: https://clusterfuzz.com/testcase?key=4914353913200640

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Stack-overflow
Crash Address: 0x7ffd2c081fd0
Crash State:
  ComputeUserRequestedAlignmentLog
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=478007:478121

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

Issue filed automatically.

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

Comment 1 by kkaluri@chromium.org, Jul 23

Labels: M-68 Test-Predator-Wrong CF-NeedsTriage
Unable to provide possible suspect using Predator, CL and Code Search.
Could someone please look into the issue.

Thank You...

Comment 2 by manoranjanr@google.com, Nov 20

Cc: enne@chromium.org
Components: Blink>Layout
Labels: -M-68 -CF-NeedsTriage M-71 M-70
enne@, just wondering do you have any inputs here?

Comment 3 by enne@chromium.org, Nov 20

Cc: e...@chromium.org
The log says blink::FontCache::CrashWithFontInfo.  CCing eae.

Comment 4 by mstensho@chromium.org, Nov 20

Owner: drott@chromium.org
Status: Assigned (was: Untriaged)
ComputeUserRequestedAlignmentLog is part of ASAN, so I don't know what's going on here. That alleged stack overflow only occurred in the first run, back in July 2018. The run from this month doesn't have this.

Both runs seem to be about DCHECK / CHECK failures in font code, though.

Comment 5 by e...@chromium.org, Dec 14

Status: WontFix (was: Assigned)
Project Member

Comment 6 by ClusterFuzz, Dec 21

Labels: Needs-Feedback
ClusterFuzz testcase 4914353913200640 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.
Project Member

Comment 7 by ClusterFuzz, Dec 22

Labels: OS-Chrome
►

Sign in to add a comment