[chromium-bugs] Issue 6418 in chromium: Chrome: Crash Report - Stack Signature: -487E8E

2009-02-27 Thread codesite-noreply
Comment #16 on issue 6418 by bugdro...@chromium.org: Chrome: Crash Report - Stack Signature: -487E8E http://code.google.com/p/chromium/issues/detail?id=6418 The following revision refers to this bug: http://src.chromium.org/viewvc/chrome?view=rev&revision=10676 --

[chromium-bugs] Issue 6418 in chromium: Chrome: Crash Report - Stack Signature: -487E8E

2009-02-17 Thread codesite-noreply
Updates: Owner: ana...@chromium.org Comment #13 on issue 6418 by s...@chromium.org: Chrome: Crash Report - Stack Signature: -487E8E http://code.google.com/p/chromium/issues/detail?id=6418 I'm passing to Ananta as I believe he's working on how to deal with Kingsoft. -- You received t

[chromium-bugs] Issue 6418 in chromium: Chrome: Crash Report - Stack Signature: -487E8E

2009-02-13 Thread codesite-noreply
Comment #12 on issue 6418 by s...@chromium.org: Chrome: Crash Report - Stack Signature: -487E8E http://code.google.com/p/chromium/issues/detail?id=6418 After talking with Ananta the current thinking is this is corruption from Kingsoft's Powerlite (cbstext.dll). He's working on how to deal wi

[chromium-bugs] Issue 6418 in chromium: Chrome: Crash Report - Stack Signature: -487E8E

2009-02-13 Thread codesite-noreply
Updates: Status: Assigned Comment #11 on issue 6418 by j...@chromium.org: Chrome: Crash Report - Stack Signature: -487E8E http://code.google.com/p/chromium/issues/detail?id=6418 It is possible that this is fixed on the trunk, or at least has not yet been seen on 2.0.162.0, see ~lafor

[chromium-bugs] Issue 6418 in chromium: Chrome: Crash Report - Stack Signature: -487E8E

2009-02-12 Thread codesite-noreply
Comment #10 on issue 6418 by divi...@hotmail.com: Chrome: Crash Report - Stack Signature: -487E8E http://code.google.com/p/chromium/issues/detail?id=6418 Add label: Assigned. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred th

[chromium-bugs] Issue 6418 in chromium: Chrome: Crash Report - Stack Signature: -487E8E

2009-02-12 Thread codesite-noreply
Updates: Owner: s...@chromium.org Comment #9 on issue 6418 by s...@chromium.org: Chrome: Crash Report - Stack Signature: -487E8E http://code.google.com/p/chromium/issues/detail?id=6418 (No comment was entered for this change.) -- You received this message because you are listed in the

[chromium-bugs] Issue 6418 in chromium: Chrome: Crash Report - Stack Signature: -487E8E

2009-02-10 Thread codesite-noreply
Comment #7 on issue 6418 by s...@chromium.org: Chrome: Crash Report - Stack Signature: -487E8E http://code.google.com/p/chromium/issues/detail?id=6418 I suspect we're keeping references to deleted RVHs too. I've added code that should help determine if that is in fact happening (see bug 6316

[chromium-bugs] Issue 6418 in chromium: Chrome: Crash Report - Stack Signature: -487E8E

2009-02-10 Thread codesite-noreply
Updates: Status: Available Owner: --- Cc: s...@chromium.org Comment #6 on issue 6418 by cr...@chromium.org: Chrome: Crash Report - Stack Signature: -487E8E http://code.google.com/p/chromium/issues/detail?id=6418 I've looked at this more, but I'm going to unassign it-- I

[chromium-bugs] Issue 6418 in chromium: Chrome: Crash Report - Stack Signature: -487E8E

2009-02-03 Thread codesite-noreply
Comment #5 on issue 6418 by cr...@chromium.org: Chrome: Crash Report - Stack Signature: -487E8E http://code.google.com/p/chromium/issues/detail?id=6418 A few notes as I look into this... The crash is happening on the process()->Init() call, likely on the reference to process_. I don't thin

[chromium-bugs] Issue 6418 in chromium: Chrome: Crash Report - Stack Signature: -487E8E

2009-02-03 Thread codesite-noreply
Updates: Owner: cr...@chromium.org Comment #4 on issue 6418 by s...@chromium.org: Chrome: Crash Report - Stack Signature: -487E8E http://code.google.com/p/chromium/issues/detail?id=6418 I'm passing to Charlie as I believe he's done a fair amount in this area. If that isn't right, ple

[chromium-bugs] Issue 6418 in chromium: Chrome: Crash Report - Stack Signature: -487E8E

2009-02-02 Thread codesite-noreply
Updates: Owner: --- Comment #3 on issue 6418 by mbel...@chromium.org: Chrome: Crash Report - Stack Signature: -487E8E http://code.google.com/p/chromium/issues/detail?id=6418 -- You received this message because you are listed in the owner or CC fields of this issue, or because you s

[chromium-bugs] Issue 6418 in chromium: Chrome: Crash Report - Stack Signature: -487E8E

2009-01-15 Thread codesite-noreply
Updates: Status: Available Owner: --- Comment #1 on issue 6418 by j...@chromium.org: Chrome: Crash Report - Stack Signature: -487E8E http://code.google.com/p/chromium/issues/detail?id=6418 (No comment was entered for this change.) -- You received this message because you are l

[chromium-bugs] Issue 6418 in chromium: Chrome: Crash Report - Stack Signature: -487E8E

2009-01-14 Thread codesite-noreply
Status: Untriaged Owner: lafo...@chromium.org Labels: Type-Bug Pri-2 OS-All Area-BrowserUI Crash stable Crash-2.0.156.1 New issue 6418 by lafo...@chromium.org: Chrome: Crash Report - Stack Signature: -487E8E http://code.google.com/p/chromium/issues/detail?id=6418 The full crash report details