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

Issue 784709 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Timeout in swiftshader_vertex_routine_fuzzer

Project Member Reported by ClusterFuzz, Nov 14 2017

Issue description

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

Fuzzer: libFuzzer_swiftshader_vertex_routine_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  swiftshader_vertex_routine_fuzzer
  
Sanitizer: address (ASAN)

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.

Note: This crash might not be reproducible with the provided testcase. That said, for the past 14 days we've been seeing this crash frequently. If you are unable to reproduce this, please try a speculative fix based on the crash stacktrace in the report. The fix can be verified by looking at the crash statistics in the report, a day after the fix is deployed. We will auto-close the bug if the crash is not seen for 14 days.
 
Cc: msrchandra@chromium.org sugoi@chromium.org pnangunoori@chromium.org
Components: Internals>GPU>SwiftShader
Labels: Test-Predator-Wrong
Owner: capn@chromium.org
Status: Assigned (was: Untriaged)
@capn -- Could you please look into this issue. 

Assigning this issue to you, as per the update we received from you in the  Issue 781505 . Please reassign if it not related to your changes.

Thanks.
Project Member

Comment 2 by ClusterFuzz, Nov 18 2017

Labels: OS-Mac

Comment 3 by capn@chromium.org, Nov 27 2017

Labels: -Pri-1 Pri-3
Will possibly improve when we address Issue swiftshader:69
Status: WontFix (was: Assigned)
We are closing all ooms and timeouts that are unreproducible. We won't be filing such bugs in future.

Comment 5 by capn@chromium.org, Apr 17 2018

Ack. Works for me.

Sign in to add a comment