http://forums.lastpass.com/viewtopic.php?f=12&t=30789&p=111719

An even faster way to cause it to crash is to setup the LastPass password manager and
restart chrome, typically crashes 1/5 times.  If it doesn't, simply close chrome and
start again until it does.

	chrome_crash.PNG 4.7 KB   View   Download

Simply starting up chrome and the crash happens. reload and it crashes again, rinse
and repeat

Lastpass is the best free password management tool available, in my opinion.

One of the last things keeping me from adopting Chrome as my primary/main browser was
the lack of extensions - and by proxy, lack of LastPass integration.

With this new instability, I'm back to Firefox for the time being, but I look
heartily forward to when this can be resolved and I can return to Chrome.

A lot of crashes for this extension in Chrome recently for me as well.

I found this bug report after reading a thread on the LastPass forum:
http://forums.lastpass.com/viewtopic.php?f=12&t=30789

Verified crashes quite often.

LastPass has been crashing in Chrome on both my Mac and Windows7 64-bit.

This is LastPass' problem, not Chromiums. LastPass should fix the issue.
These bug reports are for CHROMIUM specific issues.

Sorry for any misunderstanding. A representative of LastPass had indicated in the
initial post that he had identified this as an issue with Chrome. Since my experience
with this person is that he is careful and knowledgeable, I took that to be as
authoritative an analysis as any other (outside of the Chrome team, at least), but I
guess we'll have to hear his rebuttal. :-)

Again, my apologies if this is a misunderstanding, and sorry I don't directly know
more technical details, but I have been experiencing the crashes.

@andrewsteed You might want to reevaluate.   How do you expect LastPass to fix
_crashes_ with JavaScript, a scripting language? This is a chromium problem.   The UI
display here is one of the compounding problems -- it really should say Chrome has
crashed while running the extension: X.   Pretending that JavaScript crashes are the
extensions' fault is just confusing.

Same here.. crashes started two days ago and know there is no way it will remain stable 
once chrome is running.

Alex

Same here it used to work now crashes. It looks like crashes if other extensions are 
installed too.

works fine on the dev channel but crashes on stable

Same thing... 

Same thing here. This happened with some recent update. Can't tell if the reason is 
Chrome or LastPass as both have been updated. REALLY missing this extension, it is 
incredibly useful!

Still constantly crashing in 4.1.249.1042 (42199)

	StillCrashingChrome.PNG 46.7 KB   View   Download

I agree with joesiegr. Lastpass cannot be causing this crash (unless the root cause is 
not a jscript problem as it appears to be. I have an issue with andrewst and his 
response as it sounds like he did not actually investigate before getting all high and 
mighty. I suggest a high pressure crow dinner.

still crashing here too

http://code.google.com/p/chromium/issues/detail?id=37606 more people experiencing this.

(No comment was entered for this change.)

 Issue 37606  has been merged into this issue.

I am experiencing the crash on both Windows 7 x64 and x32. It crashes at least once per 
session. I've been using Chrome mainly for speed, and really would prefer not to revert 
to Firefox or, God forbid, IE. Please address this ASAP!

Yet another occurrence on Win7-64. Started happening for me on 25 Mar 2010. Was fine 
before that.

Could this be related to  issue 29245 ?

Crashing upon starting a browser session, typically consistently.  Rarely crashes again 
once I reload the extension.  Once it successfully loads, it does not crash mid 
session.  In case the crash is caused by an identical root problem, I have also had 
frequent crashes of the Lazarus extension that began simultaneous to the genesis of the 
LastPass issues.

Just started use of Chrome under Win7 64-bit Home Premium.  Set home page to
LastPass; last pass extension crashes regularly (almost every time) on startup,
though Chrome does not crash. Reloading extension typically results in another crash
of the extension. Using latest install of LastPass for the three browsers (v1.66.0)
and Chrome v5.0.356.2. Using Firefox while waiting for fix--I like Chrome, but really
can't visit sites anymore w/o access to LastPass.

Thanks for all of the confirmations all.  Aaron managed to reproduce the crash locally, 
so we should be able to get a fix together soon.

Concur with most of the comments. Work computer Vista + Chrome - LastPass working well. 
Home Win7 65 + Chrome, start crash, crash, crash. Win 7, LastPass & Chrome: 3 great 
platforms, hate to have to choose.

Sorry typo above, Win7 64

I'm one of the thousands affected by the crash problem and the problem of being 
involuntarily signed out of LP (have to sing in again, sometimes within minutes of the 
first sign in).  I like Chrome but Firefox accommodates Last Pass better--also Zotero, 
which has not yet been adapted for Chrome.

We appreciate the patience you've all given us so far.  As I mentioned my previous 
comment, we have a fix together and should be able to get it out in a patch soon.

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=42812 

------------------------------------------------------------------------
r42812 | aa@chromium.org | 2010-03-26 13:25:17 -0700 (Fri, 26 Mar 2010) | 9 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/render_messages.h?r1=42812&r2=42811

Write and read content blocked flag. This should have resulted
in random showing/hiding of the blocked url bar notification
when databases were in use.

It also caused lots of crashes.

BUG=38857

Review URL: http://codereview.chromium.org/1458001
------------------------------------------------------------------------

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=42816 

------------------------------------------------------------------------
r42816 | aa@chromium.org | 2010-03-26 13:43:36 -0700 (Fri, 26 Mar 2010) | 10 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/branches/249/src/chrome/common/render_messages.h?r1=42816&r2=42815

Reapply Issue 1458001 on 249 branch directly.

Write and read content blocked flag. This should have resulted 
in random showing/hiding of the blocked url bar notification 
when databases were in use. 

It also caused lots of crashes. 

BUG=38857

------------------------------------------------------------------------

 Issue 32068  has been merged into this issue.

LastPass has gone from crashing once, maybe twice, at the beginning of a browsing 
session to crashing four or more times upon beginning a browsing session.  Again, after   
LastPass finally successfully loads, it does not crash midway during a session. The 
increase in the intensity of the problem began roughly 24 hours ago.

(No comment was entered for this change.)

Issue 42971 has been merged into this issue.

This issue is not fixed. With LastPass installed, Chromium (trunk/win) crashes 100% of time on startup. Without LastPass installed, there's no crash. Bug 
42971 has a stack trace from Chrome/Mac that seems related to HTML5 DBs. The stack trace I get on Windows doesn't seem related to DBs, but both extensions 
(LassPass and Lazarus (https://chrome.google.com/extensions/detail/loljledaigphbcpfhfmgopdkppkifgno)) do use DBs. I'll take a look, but at the moment I have 
no clue what might be wrong, so any hint/idea would be greatly appreciated.

Win stack trace:
 	chrome.dll!DebugUtil::BreakDebugger()  Line 225	C++
 	chrome.dll!logging::LogMessage::~LogMessage()  Line 572	C++
 	chrome.dll!`anonymous namespace'::ExtensionImpl::StartRequest(const v8::Arguments & args={...})  Line 460	C++
 	chrome.dll!v8::internal::HandleApiCallHelper<0>(v8::internal::`anonymous-namespace'::BuiltinArguments<1> args={...})  Line 971 + 0x13 bytes	C++
 	chrome.dll!v8::internal::Builtin_Impl_HandleApiCall(v8::internal::`anonymous-namespace'::BuiltinArguments<1> args={...})  Line 988 + 0xd bytes	C++
 	chrome.dll!v8::internal::Builtin_HandleApiCall(v8::internal::`anonymous-namespace'::BuiltinArguments<1> args={...})  Line 987 + 0x18 bytes	C++
 	010d01ee()	
 	chrome.dll!v8::internal::Invoke(bool construct=false, v8::internal::Handle<v8::internal::JSFunction> func={...}, 
v8::internal::Handle<v8::internal::Object> receiver={...}, int argc=1, v8::internal::Object * * * args=0x003add58, bool * has_pending_exception=0x003adc2f)  
Line 95 + 0x19 bytes	C++
 	chrome.dll!v8::internal::Execution::Call(v8::internal::Handle<v8::internal::JSFunction> func={...}, v8::internal::Handle<v8::internal::Object> 
receiver={...}, int argc=1, v8::internal::Object * * * args=0x003add58, bool * pending_exception=0x003adc2f)  Line 121 + 0x1f bytes	C++
 	chrome.dll!v8::Function::Call(v8::Handle<v8::Object> recv={...}, int argc=1, v8::Handle<v8::Value> * argv=0x003add58)  Line 2628 + 0x1d bytes	C++
 	chrome.dll!WebCore::V8Proxy::callFunction(v8::Handle<v8::Function> function={...}, v8::Handle<v8::Object> receiver={...}, int argc=1, 
v8::Handle<v8::Value> * args=0x003add58)  Line 493 + 0x1f bytes	C++
 	chrome.dll!WebCore::V8LazyEventListener::callListenerFunction(WebCore::ScriptExecutionContext * context=0x01223034, v8::Handle<v8::Value> 
jsEvent={...}, WebCore::Event * event=0x012693c0)  Line 69 + 0x26 bytes	C++
 	chrome.dll!WebCore::V8AbstractEventListener::invokeEventHandler(WebCore::ScriptExecutionContext * context=0x01223034, WebCore::Event * 
event=0x012693c0, v8::Handle<v8::Value> jsEvent={...})  Line 150 + 0x1f bytes	C++
 	chrome.dll!WebCore::V8AbstractEventListener::handleEvent(WebCore::ScriptExecutionContext * context=0x01223034, WebCore::Event * event=0x012693c0)  
Line 94	C++
 	chrome.dll!WebCore::EventTarget::fireEventListeners(WebCore::Event * event=0x012693c0, WebCore::EventTargetData * d=0x011b98ac, 
WTF::Vector<WebCore::RegisteredEventListener,1> & entry={...})  Line 329 + 0x35 bytes	C++
 	chrome.dll!WebCore::EventTarget::fireEventListeners(WebCore::Event * event=0x012693c0)  Line 295	C++
 	chrome.dll!WebCore::DOMWindow::dispatchEvent(WTF::PassRefPtr<WebCore::Event> prpEvent={...}, WTF::PassRefPtr<WebCore::EventTarget> prpTarget={...})  
Line 1444 + 0x11 bytes	C++
 	chrome.dll!WebCore::DOMWindow::dispatchLoadEvent()  Line 1400	C++
 	chrome.dll!WebCore::Document::dispatchWindowLoadEvent()  Line 3141	C++
 	chrome.dll!WebCore::Document::implicitClose()  Line 1844	C++
 	chrome.dll!WebCore::FrameLoader::checkCallImplicitClose()  Line 1068	C++
 	chrome.dll!WebCore::FrameLoader::checkCompleted()  Line 1017	C++
 	chrome.dll!WebCore::FrameLoader::loadDone()  Line 968	C++
 	chrome.dll!WebCore::DocLoader::setLoadInProgress(bool load=false)  Line 336	C++
 	chrome.dll!WebCore::Loader::Host::didFinishLoading(WebCore::SubresourceLoader * loader=0x0126dc00)  Line 414	C++
 	chrome.dll!WebCore::SubresourceLoader::didFinishLoading()  Line 194 + 0x21 bytes	C++
 	chrome.dll!WebCore::ResourceLoader::didFinishLoading(WebCore::ResourceHandle * __formal=0x036c9dc0)  Line 443 + 0xf bytes	C++
 	chrome.dll!WebCore::ResourceHandleInternal::didFinishLoading(WebKit::WebURLLoader * __formal=0x011a0d40)  Line 191 + 0x25 bytes	C++
 	chrome.dll!webkit_glue::WebURLLoaderImpl::Context::OnCompletedRequest(const URLRequestStatus & status={...}, const 
std::basic_string<char,std::char_traits<char>,std::allocator<char> > & security_info="")  Line 574 + 0x1e bytes	C++
 	chrome.dll!ResourceDispatcher::OnRequestComplete(int request_id=15, const URLRequestStatus & status={...}, const 
std::basic_string<char,std::char_traits<char>,std::allocator<char> > & security_info="")  Line 467 + 0x17 bytes	C++
 	chrome.dll!DispatchToMethod<ResourceDispatcher,void (__thiscall ResourceDispatcher::*)(int,URLRequestStatus const 
&,std::basic_string<char,std::char_traits<char>,std::allocator<char> > const 
&),int,URLRequestStatus,std::basic_string<char,std::char_traits<char>,std::allocator<char> > >(ResourceDispatcher * obj=0x011ade10, void (int, const 
URLRequestStatus &, const std::basic_string<char,std::char_traits<char>,std::allocator<char> > &)* method=0x58cd8670, const 
Tuple3<int,URLRequestStatus,std::basic_string<char,std::char_traits<char>,std::allocator<char> > > & arg={...})  Line 435 + 0x1c bytes	C++
 	chrome.dll!IPC::MessageWithTuple<Tuple3<int,URLRequestStatus,std::basic_string<char,std::char_traits<char>,std::allocator<char> > > 
>::Dispatch<ResourceDispatcher,void (__thiscall ResourceDispatcher::*)(int,URLRequestStatus const 
&,std::basic_string<char,std::char_traits<char>,std::allocator<char> > const &)>(const IPC::Message * msg=0x012764a8, ResourceDispatcher * obj=0x011ade10, 
void (int, const URLRequestStatus &, const std::basic_string<char,std::char_traits<char>,std::allocator<char> > &)* func=0x58cd8670)  Line 1020 + 0x11 bytes	
C++
>	chrome.dll!ResourceDispatcher::DispatchMessageW(const IPC::Message & message={...})  Line 536 + 0x12 bytes	C++
 	chrome.dll!ResourceDispatcher::OnMessageReceived(const IPC::Message & message={...})  Line 303	C++
 	chrome.dll!ChildThread::OnMessageReceived(const IPC::Message & msg={...})  Line 124 + 0x19 bytes	C++
 	chrome.dll!IPC::ChannelProxy::Context::OnDispatchMessage(const IPC::Message & message={...})  Line 204 + 0x19 bytes	C++
 	chrome.dll!DispatchToMethod<IPC::ChannelProxy::Context,void (__thiscall IPC::ChannelProxy::Context::*)(IPC::Message const 
&),IPC::Message>(IPC::ChannelProxy::Context * obj=0x011bc540, void (const IPC::Message &)* method=0x57cd10b0, const Tuple1<IPC::Message> & arg={...})  Line 
422 + 0xf bytes	C++
 	chrome.dll!RunnableMethod<IPC::ChannelProxy::Context,void (__thiscall IPC::ChannelProxy::Context::*)(IPC::Message const &),Tuple1<IPC::Message> 
>::Run()  Line 296 + 0x1e bytes	C++
 	chrome.dll!MessageLoop::RunTask(Task * task=0x01276480)  Line 328 + 0xf bytes	C++
 	chrome.dll!MessageLoop::DeferOrRunPendingTask(const MessageLoop::PendingTask & pending_task={...})  Line 339	C++
 	chrome.dll!MessageLoop::DoWork()  Line 443 + 0xc bytes	C++
 	chrome.dll!base::MessagePumpDefault::Run(base::MessagePump::Delegate * delegate=0x003aed98)  Line 23 + 0xf bytes	C++
 	chrome.dll!MessageLoop::RunInternal()  Line 204 + 0x2a bytes	C++
 	chrome.dll!MessageLoop::RunHandler()  Line 177	C++
 	chrome.dll!MessageLoop::Run()  Line 155	C++
 	chrome.dll!RendererMain(const MainFunctionParams & parameters={...})  Line 295	C++
 	chrome.dll!ChromeMain(HINSTANCE__ * instance=0x01310000, sandbox::SandboxInterfaceInfo * sandbox_info=0x003af6f4, wchar_t * command_line=0x004530a4)  
Line 734 + 0xc bytes	C++
 	chrome.exe!MainDllLoader::Launch(HINSTANCE__ * instance=0x01310000, sandbox::SandboxInterfaceInfo * sbox_info=0x003af6f4)  Line 200 + 0x1d bytes	
C++
 	chrome.exe!wWinMain(HINSTANCE__ * instance=0x01310000, HINSTANCE__ * __formal=0x00000000, HINSTANCE__ * __formal=0x00000000, HINSTANCE__ * 
__formal=0x00000000)  Line 46 + 0x10 bytes	C++
 	chrome.exe!__tmainCRTStartup()  Line 324 + 0x35 bytes	C
 	chrome.exe!wWinMainCRTStartup()  Line 196	C
 	kernel32.dll!@BaseThreadInitThunk@12()  + 0xe bytes	
 	ntdll.dll!___RtlUserThreadStart@8()  + 0x23 bytes	
 	ntdll.dll!__RtlUserThreadStart@8()  + 0x1b bytes	

I get the same stack trace when installing LastPass (from lastpass.com, extension for 
chrome, no binary, v1.68.8).

Re-assigning to Aaron since this looks like an extensions problem.

The crash happens in extension_process_bindings.cc, line 459: value_args has type_ = 
TYPE_DICTIONARY instead of TYPE_LIST. The value is: {dictionary_=[1](("0",0x004f25d0 
dictionary_=[1](("popup",0x004f2630 {value_="" })) })) }

Once this bug is fixed it should be merged into the 5.0.375.xx branch: it is the top 
cause of non-plugin crashes on Mac.

(No comment was entered for this change.)

The check was added by arv in http://src.chromium.org/viewvc/chrome?
view=rev&revision=47972. CC-ing arv.

This was fixed by Rafael in http://src.chromium.org/viewvc/chrome?view=rev&revision=48212

Not so fast, I find it hard to believe that code made it into Chrome 5, which branched 
awhile ago. Dumi, are you sure that r47972 is related?

Fix needs merging.

Hmm, this code didn't make to the 375 branch. So I guess  bug 32068  is a different 
problem. I'll un-duplicate it and debug it separately. Sorry for the noise -- the stack 
traces looked similar.

Bug 42971, that is.

Raf, can you take this one?

arv: This was fixed by Rafael in http://src.chromium.org/viewvc/chrome?
view=rev&revision=48212

nope, still seeing this bug on trunk.

This appears to be another instance of us using a public function that gets clobbered 
by the extension or a library it's using (JSON.stringify, this time).

Patch coming. Will probably need to get merged to stable & beta.

I'll also do an audit of extension_process_bindings.js and renderer_process_bindings.js 
to see if there's any other places that we're at risk of this.

Raf: How can these get clobbered? What context is extension_process_bindings running in? If it is running in the 
extension context, is it run before any of the extension code? If so we should store the builtins as soon as 
possible to prevent any mishap in the future.

Yeah, it runs in the extension context, but it is run before any extension code. 
Storing builtins was exactly my plan. I'll send the review to you.

 Issue 44993  has been merged into this issue.

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=48667 

------------------------------------------------------------------------
r48667 | rafaelw@chromium.org | 2010-06-01 15:33:23 -0700 (Tue, 01 Jun 2010) | 6 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/renderer/resources/event_bindings.js?r1=48667&r2=48666
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/renderer/resources/extension_process_bindings.js?r1=48667&r2=48666
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/renderer/resources/renderer_extension_bindings.js?r1=48667&r2=48666
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/api_test/messaging/connect/page.js?r1=48667&r2=48666
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/api_test/messaging/connect/test.html?r1=48667&r2=48666

Prevent extensions from clobbering JSON implementation that extension calls use

BUG=38857
TEST=none

Review URL: http://codereview.chromium.org/2387002
------------------------------------------------------------------------

Yes, please merge to 375.

 Issue 45917  has been merged into this issue.

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=49571 

------------------------------------------------------------------------
r49571 | rafaelw@google.com | 2010-06-11 12:23:42 -0700 (Fri, 11 Jun 2010) | 9 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/branches/375/src/chrome/renderer/resources/event_bindings.js?r1=49571&r2=49570
   M http://src.chromium.org/viewvc/chrome/branches/375/src/chrome/renderer/resources/extension_process_bindings.js?r1=49571&r2=49570
   M http://src.chromium.org/viewvc/chrome/branches/375/src/chrome/renderer/resources/renderer_extension_bindings.js?r1=49571&r2=49570
   M http://src.chromium.org/viewvc/chrome/branches/375/src/chrome/test/data/extensions/api_test/messaging/connect/page.js?r1=49571&r2=49570
   M http://src.chromium.org/viewvc/chrome/branches/375/src/chrome/test/data/extensions/api_test/messaging/connect/test.html?r1=49571&r2=49570

Merge 48667 - Prevent extensions from clobbering JSON implementation that extension calls use

BUG=38857
TEST=none

Review URL: http://codereview.chromium.org/2387002

TBR=rafaelw@chromium.org
Review URL: http://codereview.chromium.org/2754014
------------------------------------------------------------------------

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=49572 

------------------------------------------------------------------------
r49572 | rafaelw@google.com | 2010-06-11 12:25:40 -0700 (Fri, 11 Jun 2010) | 8 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/branches/375/src/chrome/renderer/resources/event_bindings.js?r1=49572&r2=49571

Merge 48843 - Change 'const' to 'var' in event_bindings.js for ECMAScript compatibility reasons.
BUG=38857
TEST=None

Review URL: http://codereview.chromium.org/2444005

TBR=ericdingle@chromium.org
Review URL: http://codereview.chromium.org/2796005
------------------------------------------------------------------------

merged to 375.

Verified in build 5.0.375.86 (Official Build 49890), issue has been fixed.

Chrome Version       : 4.1.249.1036 (41514)
URLs (if applicable) : n/a

<b>What steps will reproduce the problem?</b>
1. Install LastPass (it usually crashes) https://chrome.google.com/extensions/detail/hdokiejnpimakedhajhdlcegeplioahd
2. If that doesn't work, uninstalling and reinstalling tends to crash more often, (so does general use). 

It should be noted that while LastPass also has a binary component, these crashes are occurring in the version released on 
the chrome extensions website without a binary component.

It was not crashing for the last few months, and the 5.X series is fine. 4.1.249.X was crashing in beta, and now in stable 
too.  Hundreds of complaints. 

Are you notified of these crashes?  We suspect that thousands are impacted.