What steps will reproduce the problem?
1. Install the extension
2. Attach the debugger to the plugin process
3. Exit Chrome
What is the expected output? What do you see instead?
Exit should be clean, but sometimes, we get a crash because the chromeTray.dll
gets unloaded while it still has code being executed in a running thread.
What version of the product are you using? On what operating system?
I use the dev channel of Chrome (so Version 23.0.1262.0 dev-m) and the latest
version of the extension (so 1.4).
Please provide any additional information below.
For some reason, even though the code I see here seem to be doing the right
thing during NP_Shutdown, when I step into it using the debugger, here's the
assembly code I see:
chromeTray!NP_Shutdown:
71bb4e50 e8ebccffff call chromeTray+0x1b40 (71bb1b40)
71bb4e55 33c0 xor eax,eax
71bb4e57 c3 ret
And so when I continue from that code, I sometimes get the following crash:
0:000> g
(28c0.2680): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=00000102 ebx=71bca764 ecx=76d10ac4 edx=00000000 esi=00000002 edi=7721cd35
eip=71bb6052 esp=035bf898 ebp=035bf8c4 iopl=0 nv up ei pl zr na pe nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246
<Unloaded_chromeTray.dll>+0x6052:
71bb6052 ?? ???
Original issue reported on code.google.com by mad@chromium.org on 18 Sep 2012 at 7:02
Original issue reported on code.google.com by
mad@chromium.orgon 18 Sep 2012 at 7:02