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

Issue 712674 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

ASSERT: span->len > 0

Project Member Reported by ClusterFuzz, Apr 18 2017

Issue description

Cc: msrchandra@chromium.org dsinclair@chromium.org
Labels: Test-Predator-Wrong-CLs M-60
Owner: tsepez@chromium.org
Status: Assigned (was: Untriaged)
This Crash State looks similar to that of Bug Id - 709470. Could some one please look into the issue and provide an update.
Thank You.
Project Member

Comment 2 by ClusterFuzz, Apr 19 2017

ClusterFuzz has detected this issue as fixed in range 465173:465186.

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

Fuzzer: libfuzzer_pdfium_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  span->len > 0
  void CFX_Renderer::render<agg::scanline_u<unsigned char> >
  void agg::render_scanlines<agg::rasterizer_scanline_aa, agg::scanline_u<unsigned
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=465150:465173
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=465173:465186

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv94anNw3unYu4A8GY6z73kLGWIBt1gqQgBSBbmxb9Yr29HWAa8gEd-4BD5vo9Dxo9xOO-jBrrvo5b3Yo9rkHTD4A_2GyRqx_3cmjoPEHmhzppBFS-5KZ8YcF1V4sM7gVhWwZgNfnxRGm01oWasxbz1qDqB0Jw6v-26j4L1dHdq4Rv1xiiRmxqNLHduKvHsOZ45guDfMrW-TtLaPiW4fEJIb7kxmsjRJbhSwPb8cZiwb10iI7TH7zhJPb_WPkCA7EsNEThNwmAQwm-2j4FQ3ll887X-70f1wiOqb0iz-BWT9VVh7f0XVp9MqpjADnDmnwLRSM4fksYMlhiBOnf8klMym4xYMbNlWuwoy3gEL70Ek28xWPSDM?testcase_id=4525665723613184


See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md 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 3 by ClusterFuzz, Apr 19 2017

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

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Labels: ClusterFuzz-Wrong
Owner: dsinclair@chromium.org
Status: Available (was: Verified)
Don't think this would have been fixed yet.
Components: Internals>Plugins>PDF
Status: WontFix (was: Available)
Bulk-WontFixing these bugs. This was a bug on ClusterFuzz side, see bug 717534. We will start seeing new testcases auto-filed in a day or two. We can't leave these open as ClusterFuzz won't autoverify them after ClusterFuzz-Wrong label.
Labels: -ClusterFuzz-Wrong
We have made a bunch of changes on ClusterFuzz side, so resetting ClusterFuzz-Wrong label.

Sign in to add a comment