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

Issue 863548 link

Starred by 3 users
Status: WontFix
Owner:
futhark@chromium.org
Closed: Dec 14
Cc:
█ y...@yoav.ws
kkaluri@chromium.org
dgozman@chromium.org
alancutter@chromium.org
style-bugs@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Float-cast-overflow in blink::ColorMediaFeatureEval

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

Fuzzer: inferno_twister
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Float-cast-overflow
Crash Address: 
Crash State:
  blink::ColorMediaFeatureEval
  blink::MediaQueryEvaluator::Eval
  blink::MediaQueryList::UpdateMatches
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=551565:556760

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Jul 13

Components: Blink>CSS
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Comment 2 by kkaluri@chromium.org, Jul 19

Cc: kkaluri@chromium.org alancutter@chromium.org
Labels: M-68
Owner: dgozman@chromium.org
Status: Assigned (was: Untriaged)
The Predator has provided 6 possible suspects 

1. Reland "Move manifest.mojom and content::Manifest to blink" by dgozman@chromium.org
2. Revert "Reland "Move manifest.mojom and content::Manifest to blink"" by dgozman@chromium.org
3. Revert "Move manifest.mojom and content::Manifest to blink" by alancutter@chromium.org
4. Reland #2 "Move manifest.mojom and content::Manifest to blink" by dgozman@chromium.org
5. Move manifest.mojom and content::Manifest to blink by dgozman@chromium.org
6. Revert "Reland #2 "Move manifest.mojom and content::Manifest to blink"" by findit-for-me@appspot.gserviceaccount.com

Assigning to dgozman@ for his maximum changes and cc'ing alancutter@ for further triage.

Comment 3 by dgozman@chromium.org, Jul 19

Cc: dgozman@chromium.org
Owner: y...@yoav.ws
Not sure how manifest changes can be related to media queries. Yoav, mind triaging this?

Comment 4 by y...@yoav.ws, Sep 5

Cc: y...@yoav.ws
Owner: futhark@chromium.org
Reassigning as I haven't dealt with MQs in a looong while, and won't have time to tackle this in the immediate future.

Rune - can you maybe take a look?

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

Status: WontFix (was: Assigned)
Non-security numeric overflow bugs are considered won't fix.
Project Member

Comment 6 by ClusterFuzz, Dec 21

Labels: Needs-Feedback
ClusterFuzz testcase 6531137871282176 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.

Comment 7 by futhark@chromium.org, Jan 1 

 Issue 918147  has been merged into this issue.
►

Sign in to add a comment