Re: Issue 434789 in chromium: Chrome: Crash Report - [chrome_elf.dll]:

11 views
Skip to first unread message

sco...@chromium.org

unread,
Dec 3, 2014, 6:34:19 PM12/3/14
to chrome-blackli...@chromium.org
Updates:
Cc: chrome-b...@chromium.org

Comment #17 on issue 434789 by sco...@chromium.org: Chrome: Crash Report -
[chrome_elf.dll]:
https://code.google.com/p/chromium/issues/detail?id=434789

Looping in chrome-blackli...@chromium.org too.

--
You received this message because you were CC'd on the issue.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

Reply to this email to add a comment.

bugd...@chromium.org

unread,
Dec 3, 2014, 7:09:32 PM12/3/14
to chrome-blackli...@chromium.org

Comment #18 on issue 434789 by bugdro...@chromium.org: Chrome: Crash Report
- [chrome_elf.dll]:
https://code.google.com/p/chromium/issues/detail?id=434789#c18

The following revision refers to this bug:

https://chromium.googlesource.com/chromium/src.git/+/ee12d5a484b6726e74ff0db64a90f651c633570c

commit ee12d5a484b6726e74ff0db64a90f651c633570c
Author: scottmg <sco...@chromium.org>
Date: Thu Dec 04 00:07:25 2014

Block Samsung Smart Security ESCORT dlls from loading into renderer

R=jsc...@chromium.org
BUG=434789

Review URL: https://codereview.chromium.org/777083002

Cr-Commit-Position: refs/heads/master@{#306725}

[modify]
http://crrev.com/ee12d5a484b6726e74ff0db64a90f651c633570c/content/common/sandbox_win.cc

robert...@chromium.org

unread,
Dec 3, 2014, 7:20:49 PM12/3/14
to chrome-blackli...@chromium.org

Comment #19 on issue 434789 by robertsh...@chromium.org: Chrome: Crash
Catching up. I didn't see any of these occurring in browser processes. Let
me know if you saw otherwise.

csh...@chromium.org

unread,
Dec 4, 2014, 10:03:12 AM12/4/14
to chrome-blackli...@chromium.org

Comment #20 on issue 434789 by csh...@chromium.org: Chrome: Crash Report -
[chrome_elf.dll]:
https://code.google.com/p/chromium/issues/detail?id=434789

I contacted a Samsung developer responsible for this dll in September, so
they've been aware that this was causing stability issues. Since the crash
rate hasn't really improved since then, adding this to the blacklist seems
correct.

sco...@chromium.org

unread,
Dec 8, 2014, 4:09:15 PM12/8/14
to chrome-blackli...@chromium.org
Updates:
Status: Fixed

Comment #21 on issue 434789 by sco...@chromium.org: Chrome: Crash Report -
[chrome_elf.dll]:
https://code.google.com/p/chromium/issues/detail?id=434789

The last crash I can see is on 41.0.2238.1 which corresponds with when #18
landed.

https://chromium.googlesource.com/chromium/src/+log/41.0.2238.1..41.0.2239.0?pretty=fuller&n=10000

So assuming there's no bad interactions reported by Conops, I think we're
good.
Reply all
Reply to author
Forward
0 new messages