Issue metadata
Sign in to add a comment
|
Abrt in allocPixels |
||||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6457502970675200 Fuzzer: marty_html_twiddler Job Type: linux_lsan_chrome_mp Platform Id: linux Crash Type: Abrt Crash Address: 0x03e900005f3e Crash State: allocPixels allocPixels allocN32Pixels Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=440242:440307 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6457502970675200 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Aug 16 2017
failing a basic pixel allocation here- passing to pdr@ (?) to double check the scrollbar code...
,
Aug 21 2017
This looks like a regression. I further bisected this to: https://chromium.googlesource.com/chromium/src/+log/835009a938d0b6c52176989221a62261ac025040..c4c7a57c10a808a2eefcc605095fe40fb75b2650 I will try to narrow this down to a specific patch.
,
Aug 30 2017
I know this seems crazy but I just manually bisected and I think this is: Remove support for the keygen tag https://chromium.googlesource.com/chromium/src/+/5d916f6c6b47472770e03cb483f06a18ca79a0c2
,
Aug 30 2017
Actually, we have a solution for this. Enne has a patch in the queue. Rsleevi, maybe spot-check to see if your patch could have had a mistake in this area, but don't worry too much.
,
Aug 30 2017
Oh, this testcase depended on having a keygen in the test file. I overlooked that and spent all day bisecting manually :( Rsleevi: nothing to see here. Don't worry about this bug.
,
Aug 30 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by msrchandra@chromium.org
, Jul 24 2017Labels: Test-Predator-Wrong-CLs M-60