Issue metadata
Sign in to add a comment
|
Crash in blink::ThreadState::freePersistentNode |
||||||||||||||||||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=6167544966938624 Fuzzer: lcamtuf_cross_fuzz Job Type: linux_asan_chrome_chromeos Platform Id: linux Crash Type: UNKNOWN READ Crash Address: 0x000000000010 Crash State: blink::ThreadState::freePersistentNode base::internal::BindState<void device::blink::BatteryMonitor_QueryNextStatus_ForwardToCallback::~BatteryMonitor Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_chromeos&range=417858:417859 Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv96tJLj_heX2zCGOAjXh5qdFDkWoBaNIwtuDJD3mzNHZgLgFnv-XSWiMEOgCfHrsFto4IulqCaELm68DF1IMAj_jXDN9PMP5LzVOB-t6UwpwJD2XgyvvVeTgGdDlPO80B3xG2ClEpZawlJ13p3jf4gbKePBWcxLFuwGeSXZkAFClLTIYxuk?testcase_id=6167544966938624 Additional requirements: Requires Gestures Issue manually filed by: ranjitkan See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Oct 5 2016
,
Oct 5 2016
keishi@: Is this also related to the per-thread heap?
,
Oct 6 2016
I don't see Workers being used in the test case so I think this is unrelated. Looks like complication during shutdown. I'm guessing the base::bind created here is being destructed after main ThreadState has detached https://cs.chromium.org/chromium/src/third_party/WebKit/Source/modules/battery/BatteryDispatcher.cpp?type=cs&sq=package:chromium&rcl=1475695348&l=23
,
Oct 6 2016
Okay. I'm working on removing the shutdown code, although it will take a couple of more time: https://codereview.chromium.org/2309153002/
,
Oct 8 2016
ClusterFuzz has detected this issue as fixed in range 423881:423995. Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6167544966938624 Fuzzer: lcamtuf_cross_fuzz Job Type: linux_asan_chrome_chromeos Platform Id: linux Crash Type: UNKNOWN READ Crash Address: 0x000000000010 Crash State: blink::ThreadState::freePersistentNode base::internal::BindState<void device::blink::BatteryMonitor_QueryNextStatus_ForwardToCallback::~BatteryMonitor Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_chromeos&range=417858:417859 Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_chromeos&range=423881:423995 Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv96tJLj_heX2zCGOAjXh5qdFDkWoBaNIwtuDJD3mzNHZgLgFnv-XSWiMEOgCfHrsFto4IulqCaELm68DF1IMAj_jXDN9PMP5LzVOB-t6UwpwJD2XgyvvVeTgGdDlPO80B3xG2ClEpZawlJ13p3jf4gbKePBWcxLFuwGeSXZkAFClLTIYxuk?testcase_id=6167544966938624 Additional requirements: Requires Gestures 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.
,
Oct 8 2016
ClusterFuzz testcase is verified as fixed, closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Nov 22 2016
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 |
|||||||||||||||||||||
Comment 1 by ranjitkan@chromium.org
, Oct 5 2016Components: Tools>Test>FindIt>CorrectResult
Labels: -Pri-1 -Type-Bug Findit-for-crash M-55 Te-Logged Pri-2 Type-Bug-Regression
Owner: sigbjo...@opera.com
Status: Assigned (was: Untriaged)