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

Issue 711418 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

ASSERT: 0 && "input type"

Project Member Reported by ClusterFuzz, Apr 13 2017

Issue description

Cc: noel@chromium.org ccameron@chromium.org
Components: Blink>Image
Labels: Test-Predator-Wrong M-59
Predator and regression range did not given any suspected CL. could some please take a look?
Thank you.

Comment 2 by noel@chromium.org, Apr 14 2017

Cc: -noel@chromium.org
Owner: noel@chromium.org
Status: Started (was: Untriaged)
Reproduced the bug locally with a DEBUG build of the qcms fuzzer.

Some assert() conditions in qcms are advisory only: they are not real errors and the code returns a failure code in all cases right after such asserts().

Fix is to disable assert() like these when running in the qcms fuzzer.  However, other assert() in qcms code are real errors: we should leave those alone.

Lemme fix it ...

Comment 4 by noel@chromium.org, Apr 14 2017

Status: Fixed (was: Started)
Project Member

Comment 5 by ClusterFuzz, Apr 14 2017

Labels: BugSource-Chromium PaintTeamTriaged-20170414

Sign in to add a comment