New issue
Advanced search Search tips

Issue 673622 link

Starred by 1 user

Issue metadata

Status: Verified
Owner: ----
Closed: Jan 2017
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Direct-leak in g_malloc

Project Member Reported by ClusterFuzz, Dec 13 2016

Issue description

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  g_malloc
  g_malloc
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_lsan_chrome_mp&range=399504:399564

Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv95V7or__8n6SCqgXFu4O8a120CnZkhvOx6I7XNRA48PJ_ZZ3GM2yLE3djNg4f--At-vleEk8fdZUl-sSxE7N3V1xLcqtCHRqGLD28DJI_cUgcp-Ne685Bm6k8aPNZwuhofhTxkplrk0IVZAdg9awC459fKk7g?testcase_id=6450388444381184


Additional requirements: Requires Gestures

Issue filed automatically.

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
 
Labels: Test-Predator-Wrong M-57
Project Member

Comment 2 by ClusterFuzz, Jan 6 2017

ClusterFuzz has detected this issue as fixed in range 440847:440849.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  g_malloc
  g_malloc
  
Sanitizer: address (ASAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_lsan_chrome_mp&range=399504:399564
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_lsan_chrome_mp&range=440847:440849

Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv95V7or__8n6SCqgXFu4O8a120CnZkhvOx6I7XNRA48PJ_ZZ3GM2yLE3djNg4f--At-vleEk8fdZUl-sSxE7N3V1xLcqtCHRqGLD28DJI_cUgcp-Ne685Bm6k8aPNZwuhofhTxkplrk0IVZAdg9awC459fKk7g?testcase_id=6450388444381184


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.
Project Member

Comment 3 by ClusterFuzz, Jan 6 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Untriaged)
ClusterFuzz testcase 6450388444381184 is verified as fixed, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

Sign in to add a comment