Issue metadata
Sign in to add a comment
|
ASSERT: GTK_IS_WIDGET (widget) |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5636787033341952 Fuzzer: attekett_surku_fuzzer Job Type: linux_tsan_chrome_mp Platform Id: linux Crash Type: ASSERT Crash Address: 0x7b040005b910 Crash State: GTK_IS_WIDGET (widget) Sanitizer: thread (TSAN) Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=553057:553059 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5636787033341952 Additional requirements: Requires Gestures Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Jul 16
,
Jul 17
This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it. If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 17
,
Jul 17
thomasanderson@ this looks similar to Issue 813449 , and might be a dupe or at least solved by the same ultimate fix. Could you take a look?
,
Jul 17
Yes I would agree that they would have the same fix
,
Jul 18
,
Aug 1
ClusterFuzz has detected this issue as fixed in range 579638:579641. Detailed report: https://clusterfuzz.com/testcase?key=5636787033341952 Fuzzer: attekett_surku_fuzzer Job Type: linux_tsan_chrome_mp Platform Id: linux Crash Type: ASSERT Crash Address: 0x7b040005b910 Crash State: GTK_IS_WIDGET (widget) Sanitizer: thread (TSAN) Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=553057:553059 Fixed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=579638:579641 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5636787033341952 Additional requirements: Requires Gestures See https://github.com/google/clusterfuzz-tools for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Aug 1
ClusterFuzz testcase 5636787033341952 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Aug 1
,
Aug 3
,
Aug 3
This bug requires manual review: M69 has already been promoted to the beta branch, so this requires manual review Please contact the milestone owner if you have questions. Owners: amineer@(Android), kariahda@(iOS), cindyb@(ChromeOS), govind@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 3
There's no CL. Not sure why sheriffbot added the merge request
,
Aug 13
,
Aug 15
,
Nov 7
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ClusterFuzz
, Jul 16Labels: Test-Predator-Auto-Components