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

Issue 623728 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Jul 2016
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

false in message_port_service.cc

Project Member Reported by ClusterFuzz, Jun 27 2016

Issue description

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6622821308694528

Fuzzer: therealholden_worker
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  false in message_port_service.cc
  content::MessagePortService::PostMessageTo
  content::MessagePortService::PostMessage
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_debug_chrome&range=173978:174317

Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv960Ew7XUKfY8Ffp6ye9bgRq9_DVlY1OuDTW1qh2Tx6r8nl1O-us_B0kUIhPTQaQFSSC3damiq8BgmFFwXJZMaGcI5qSikSK5yPzXcljZgdgTs83RtGZIRDyrZkeVb5jfLpkfR141Th9BJU1STvarXcgC_XvxA?testcase_id=6622821308694528


Additional requirements: Requires HTTP

Filer: mmohammad

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
 
Owner: alokp@chromium.org
Status: Assigned (was: Available)

Suspected CL could behttps://chromium.googlesource.com/chromium/src/+/1f4996786dd7ab2e5d7f51c72f9309ee50aeb176%5E%21/media/audio/audio_manager.cc


Last updated by alokp @ weeks ago , please have a look and reassign if needed.

Thank you.

Comment 2 by alokp@chromium.org, Jun 28 2016

Owner: mmohammad@chromium.org
WARNING:audio_manager.cc(297)] Multiple instances of AudioManager detected

This is normal for tests - not for production. The main issue is not AudioManager but MessagePortService.
Project Member

Comment 3 by ClusterFuzz, Jul 1 2016

ClusterFuzz has detected this testcase as flaky and is unable to reproduce it in the original crash revision. Skipping fixed testing check and marking it as potentially fixed.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6622821308694528

Fuzzer: therealholden_worker
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  false in message_port_service.cc
  content::MessagePortService::PostMessageTo
  content::MessagePortService::PostMessage
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_debug_chrome&range=173978:174317

Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv960Ew7XUKfY8Ffp6ye9bgRq9_DVlY1OuDTW1qh2Tx6r8nl1O-us_B0kUIhPTQaQFSSC3damiq8BgmFFwXJZMaGcI5qSikSK5yPzXcljZgdgTs83RtGZIRDyrZkeVb5jfLpkfR141Th9BJU1STvarXcgC_XvxA?testcase_id=6622821308694528


Additional requirements: Requires HTTP

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Status: WontFix (was: Assigned)
looks this test case is flaky so marking as won't fix, we re-open when it continuesly fails . Thanks
Project Member

Comment 5 by sheriffbot@chromium.org, Nov 22 2016

Labels: -Restrict-View-EditIssue
Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment