New issue
Advanced search Search tips

Issue 920168 link

Starred by 2 users
Status: Assigned
Owner:
thomasanderson@chromium.org
Cc:
kkaluri@chromium.org
mmoroz@chromium.org
awhalley@google.com
mbarbe...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Data race in libgobject-2.0.so.0

Project Member Reported by ClusterFuzz, Jan 9 
Detailed report: https://clusterfuzz.com/testcase?key=6302272933593088

Fuzzer: attekett_dom_fuzzer
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Data race WRITE 8
Crash Address: 0x7b1000120300
Crash State:
  libgobject-2.0.so.0
  
Sanitizer: thread (TSAN)

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.
Project Member

Comment 1 by ClusterFuzz, Jan 9

Labels: M-73 Fuzz-Blocker ReleaseBlock-Beta
This crash occurs very frequently on linux platform and is likely preventing the fuzzer attekett_dom_fuzzer from making much progress. Fixing this will allow more bugs to be found.

Marking this bug as a blocker for next Beta release.

If this is incorrect, please add ClusterFuzz-Wrong label and remove the ReleaseBlock-Beta label.

Comment 2 by kkaluri@chromium.org, Jan 10

Cc: kkaluri@chromium.org
Components: UI>Browser
Labels: M-72 Test-Predator-Wrong
Owner: thomasanderson@chromium.org
Status: Assigned (was: Untriaged)
With reference to the  Issue 813449 , assigning it to the thomasanderson@ for further triage.

Comment 3 by pnangunoori@chromium.org, Jan 11 

Friendly ping to look into this issue and to provide further update on this issue as it has been marked as a Beta blocker.

Thanks!

Comment 4 by abdulsyed@google.com, Jan 14

Cc: awhalley@google.com
+awhalley@ does this seem right right priority for this issue? Currently marked as RB-Beta

Comment 5 by awhalley@google.com, Jan 15

Cc: mmoroz@chromium.org
Not directly a security issue, mmoroz@ - what's the usual process for clusterfuzz issues like this?

Comment 6 by mmoroz@chromium.org, Jan 15

Cc: mbarbe...@chromium.org
Labels: -M-72 M-74
Marty, do you know why this once is marked as a release blocker? Because it's a fuzz blocker, perhaps?

Andrew, I think changing the milestone is fine here.

Comment 7 by mbarbella@google.com, Jan 15 

In this case it seems like it's because it's marked as a fuzzing blocker, yeah. Since this is a race and might be difficult to fix I don't have any objection to removing the ReleaseBlock label for this bug.

Comment 8 by jmukthavaram@chromium.org, Today (15 hours ago) 

Friendly ping to get an update on this issue as it is marked as beta blocker.
Thanks..!

Comment 9 by thomasanderson@chromium.org, Today (13 hours ago)

Labels: -ReleaseBlock-Beta
►

Sign in to add a comment