Issue metadata
Sign in to add a comment
|
Crash in content::MHTMLGenerationManager::OnFileClosed |
||||||||||||||||||||||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=5891764645003264 Fuzzer: meacer_extension_apis Job Type: linux_asan_chrome_chromeos Platform Id: linux Crash Type: UNKNOWN READ Crash Address: 0x000000000110 Crash State: content::MHTMLGenerationManager::OnFileClosed void base::internal::ReplyAdapter<long, long> base::PostTaskAndReplyRelay::RunReplyAndSelfDestruct Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_chromeos&range=386428:386438 Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv96EsjuTch_zFBipf2EDDclB1hc8idVxK8V2dTxaOWpYNTUHq7jW_p1JdnJ9wwGW_yzvYWKIs5pbMiCidIpm07wNBOqjGxrj-S1GsX4SSrQYk_YDf9qJHFyN8GXJ7V2Yk4tAC0Mg817af4HsH1oSubk68G9wWA?testcase_id=5891764645003264 Filer: rnimmagadda See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Jul 26 2016
This seems to be a dupe of issue 612098 (but this should have been fixed last week).
,
Jul 26 2016
,
Jul 26 2016
I should just stop doing cleanup CLs. ;)
,
Jul 26 2016
ClusterFuzz report says the crash revision for Chromium is r406944. This is earlier than the fix from issue 612098 (r407244).
,
Jul 27 2016
ClusterFuzz has detected this issue as fixed in range 407004:407711. Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5891764645003264 Fuzzer: meacer_extension_apis Job Type: linux_asan_chrome_chromeos Platform Id: linux Crash Type: UNKNOWN READ Crash Address: 0x000000000110 Crash State: content::MHTMLGenerationManager::OnFileClosed void base::internal::ReplyAdapter<long, long> base::PostTaskAndReplyRelay::RunReplyAndSelfDestruct Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_chromeos&range=386428:386438 Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_chromeos&range=407004:407711 Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv96EsjuTch_zFBipf2EDDclB1hc8idVxK8V2dTxaOWpYNTUHq7jW_p1JdnJ9wwGW_yzvYWKIs5pbMiCidIpm07wNBOqjGxrj-S1GsX4SSrQYk_YDf9qJHFyN8GXJ7V2Yk4tAC0Mg817af4HsH1oSubk68G9wWA?testcase_id=5891764645003264 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 18 2016
,
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 rnimmagadda@chromium.org
, Jul 26 2016Labels: -Pri-1 -Type-Bug M-54 Findit-for-crash Te-Logged Pri-2 Type-Bug-Regression
Owner: thestig@chromium.org
Status: Assigned (was: Untriaged)