search

mariusvam / omaha

Automatically exported from code.google.com/p/omaha
Apache License 2.0
1 stars 0 forks source link

An unhandled win32 exception occurred in GoogleUpdate.exe [3280] occurs repeatedly on Windows Server 2003 SP2 #39

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. The problem happens periodically (maybe every few hours) without any user 
intervention.

What is the expected output? What do you see instead?

Expected output: nothing.
Actual output: Visual Studio JIT Debugger screen(s) come up saying An unhandled 
win32 exception occurred in GoogleUpdate.exe [3280].  I have seen as many as 20 
instances of this screen at once.

What version of the product are you using? On what operating system?

Google Chrome and Gmail Notifier are the only Google software installed on the 
machine I believe.

Please provide any additional information below.

OS is MS Windows Server 2003 SP2

I have uninstalled and reinstalled Google Chrome to no effect.

Original issue reported on code.google.com by brianuc...@gmail.com on 21 Jul 2012 at 2:40

GoogleCodeExporter commented 8 years ago 
We're investigating this now.  What version of Chrome are you currently running?

Original comment by ryanmyers@google.com on 22 Jul 2012 at 9:26

GoogleCodeExporter commented 8 years ago

Original comment by so...@google.com on 22 Jul 2012 at 9:33

GoogleCodeExporter commented 8 years ago 
When I go to About Google Chrome it shows: Google Chrome is up to date 
(20.0.1132.57).  And it throws this error.

Original comment by brianuc...@gmail.com on 22 Jul 2012 at 10:55

GoogleCodeExporter commented 8 years ago 
If you have a JIT debugger installed on that machine, can you make a dump for 
us?

Original comment by ryanmyers@google.com on 23 Jul 2012 at 8:36

GoogleCodeExporter commented 8 years ago 
Unfortunately, I don't have a working JIT debugger.  The Visual Studio on there 
is a 90 day trial that's long expired.

Original comment by brianuc...@gmail.com on 23 Jul 2012 at 10:16

GoogleCodeExporter commented 8 years ago 
We haven't been able to reproduce this locally, so we're really dependent on a 
dump at the moment.  (Normally, Google Update has its own exception handler 
that will create a minidump and report it to us; however, if you're seeing this 
dialogue, that implies that the exception handler isn't functioning for some 
reason.)

If you feel comfortable with installing a new debugger on your machine, you can 
install WinDBG (the standard Microsoft debugger) here:

http://msdn.microsoft.com/en-us/windows/hardware/gg463009.aspx

When it crashes and you get the option to debug with WinDBG, you can run .dump 
/ma to generate a full minidump.

Barring that, it would be useful to know what version of Google Update you have 
installed.  Depending on whether your apps are installed per-user or 
per-machine, Google Update will live in one of these two directories:

%ProgramFiles%\Google\Update
Users\%user%\AppData\Local\Google\Update

There will be a GoogleUpdate.exe in the directory's root, and then a 
subdirectory for the currently installed version.  We need the version of both 
GoogleUpdate.exe and the version of Goopdate.dll inside the version 
subdirectory.

Original comment by ryanmyers@google.com on 1 Aug 2012 at 6:03

GoogleCodeExporter commented 8 years ago 
In addition to what Ryan is saying, I wonder if you could also use 
ProcessExplorer (http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx) 
or even Windows Task Manager to generate a dump. Find the process that has 
crashed, right click, and generate the full dump. There could be more than one 
GoogleUpdate process, in that case, it could be easier to dump them all.

Original comment by so...@chromium.org on 1 Aug 2012 at 6:30

GoogleCodeExporter commented 8 years ago 
Attached is a dump generated by ProcessExplorer.  Thanks for the suggestion.

Original comment by brianuc...@gmail.com on 3 Aug 2012 at 2:18

Attachments:

GoogleCodeExporter commented 8 years ago 
For some reason, I can't use the dump provided, I apologize for that. The best 
way to continue would be by following Ryan's advice above. I am sorry for the 
trouble.

Original comment by so...@chromium.org on 3 Aug 2012 at 5:29

GoogleCodeExporter commented 8 years ago 
I was able to load the minidump, but there's no sign of it actually having a 
crash in it -- appears to be a normally running Core process.  Might have been 
another process.

0:000> ~* kb

.  0  Id: 698.1f30 Suspend: 0 Teb: 7ffdf000 Unfrozen
ChildEBP RetAddr  Args to Child              
0012f648 7739c811 7739c844 0012f68c 00000000 ntdll!KiFastSystemCallRet
0012f668 18063485 0012f68c 00000000 00000000 user32!NtUserGetMessage+0xc
0012f6a8 180632da 0012fc48 00000000 003e5ac0 goopdate!omaha::Core::DoRun+0x89 
[p:\p\agents\hpac3.eem\recipes\164139668\base\branches\omaha_red_release_branch\
googleclient\omaha\core\core.cc @ 301]
0012f714 18062e90 0012fc48 003e7608 00000001 goopdate!omaha::Core::DoMain+0x307 
[p:\p\agents\hpac3.eem\recipes\164139668\base\branches\omaha_red_release_branch\
googleclient\omaha\core\core.cc @ 253]
0012f744 18014101 0012fc48 00000000 00000001 goopdate!omaha::Core::Main+0x15 
[p:\p\agents\hpac3.eem\recipes\164139668\base\branches\omaha_red_release_branch\
googleclient\omaha\core\core.cc @ 81]
0012fe84 18013abe 0012febb 003e5ac0 180b2fd8 
goopdate!omaha::detail::GoopdateImpl::ExecuteMode+0x436 
[p:\p\agents\hpac3.eem\recipes\164139668\base\branches\omaha_red_release_branch\
googleclient\omaha\goopdate\goopdate.cc @ 732]
0012feb0 18013779 00020ae8 00154550 0012feec 
goopdate!omaha::detail::GoopdateImpl::DoMain+0x1dd 
[p:\p\agents\hpac3.eem\recipes\164139668\base\branches\omaha_red_release_branch\
googleclient\omaha\goopdate\goopdate.cc @ 598]
0012fecc 180010f8 18000000 00020ae8 00000001 
goopdate!omaha::detail::GoopdateImpl::Main+0x20 
[p:\p\agents\hpac3.eem\recipes\164139668\base\branches\omaha_red_release_branch\
googleclient\omaha\goopdate\goopdate.cc @ 432]
0012ff00 00401603 00020ae8 00000001 00000ece goopdate!DllEntry+0x8d 
[p:\p\agents\hpac3.eem\recipes\164139668\base\branches\omaha_red_release_branch\
googleclient\omaha\goopdate\main.cc @ 65]
0012ff28 00403bb8 00400000 00000000 00020bb2 GoogleUpdate!wWinMain+0x9a 
[p:\p\agents\hpac3.eem\recipes\144640958\base\branches\omaha_red_release_branch\
googleclient\omaha\google_update\winmain.cc @ 213]
0012ffc0 77e6f23b 00000000 00000000 7ffd8000 
GoogleUpdate!__tmainCRTStartup+0x176 
[f:\dd\vctools\crt_bld\self_x86\crt\src\crt0.c @ 324]
0012fff0 00000000 00403c21 00000000 00000000 kernel32!BaseProcessStart+0x23

   1  Id: 698.1f94 Suspend: 0 Teb: 7ffdd000 Unfrozen
ChildEBP RetAddr  Args to Child              
00cfff18 7c827b79 77e61d1e 00000128 00000000 ntdll!KiFastSystemCallRet
00cfff1c 77e61d1e 00000128 00000000 00000000 ntdll!ZwWaitForSingleObject+0xc
00cfff8c 77e61c8d 00000128 ffffffff 00000000 kernel32!WaitForSingleObjectEx+0xac
00cfffa0 18047d23 00000128 ffffffff 00000000 kernel32!WaitForSingleObject+0x12
00cfffb8 77e6482f 003e65a0 00000000 00000000 
goopdate!google_breakpad::ExceptionHandler::ExceptionHandlerThreadMain+0x19 
[p:\p\agents\hpac3.eem\recipes\164139668\base\branches\omaha_red_release_branch\
googleclient\omaha\third_party\breakpad\src\client\windows\handler\exception_han
dler.cc @ 328]
00cfffec 00000000 18047d0a 003e65a0 00000000 kernel32!BaseThreadStart+0x34

   2  Id: 698.1580 Suspend: 0 Teb: 7ffdc000 Unfrozen
ChildEBP RetAddr  Args to Child              
00f6ff9c 7c826db9 7c83d29a 00000001 00f6ffb0 ntdll!KiFastSystemCallRet
00f6ffa0 7c83d29a 00000001 00f6ffb0 00000000 ntdll!NtDelayExecution+0xc
00f6ffb8 77e6482f 00000000 00000000 00000000 ntdll!RtlpTimerThread+0x47
00f6ffec 00000000 7c83d253 00000000 00000000 kernel32!BaseThreadStart+0x34

   3  Id: 698.e0c Suspend: 0 Teb: 7ffdb000 Unfrozen
ChildEBP RetAddr  Args to Child              
0106ff70 7c827649 7c839dc8 000001a8 0106ffb0 ntdll!KiFastSystemCallRet
0106ff74 7c839dc8 000001a8 0106ffb0 0106ffb4 ntdll!NtRemoveIoCompletion+0xc
0106ffb8 77e6482f 00000000 00000000 00000000 ntdll!RtlpWorkerThread+0x3d
0106ffec 00000000 7c839d8b 00000000 00000000 kernel32!BaseThreadStart+0x34

   4  Id: 698.1154 Suspend: 0 Teb: 7ffda000 Unfrozen
ChildEBP RetAddr  Args to Child              
0116fcec 7c827b69 7c83c60e 00000002 0116fd34 ntdll!KiFastSystemCallRet
0116fcf0 7c83c60e 00000002 0116fd34 00000001 ntdll!NtWaitForMultipleObjects+0xc
0116ffb8 77e6482f 00000000 00000000 00000000 ntdll!RtlpWaitThread+0x161
0116ffec 00000000 7c83c4c3 00000000 00000000 kernel32!BaseThreadStart+0x34

   5  Id: 698.1db8 Suspend: 0 Teb: 7ffd9000 Unfrozen
ChildEBP RetAddr  Args to Child              
0126fe94 7c827b69 77e6202c 00000003 0126fee4 ntdll!KiFastSystemCallRet
0126fe98 77e6202c 00000003 0126fee4 00000001 ntdll!NtWaitForMultipleObjects+0xc
0126ff40 77e62fbe 00000003 003e6df8 00000000 
kernel32!WaitForMultipleObjectsEx+0x11a
0126ff5c 18075e6b 00000003 003e6df8 00000000 
kernel32!WaitForMultipleObjects+0x18
0126ff88 18011a7b 00000000 00000000 003e744c 
goopdate!omaha::detail::RegistryMonitorImpl::Run+0x98 
[p:\p\agents\hpac3.eem\recipes\164139668\base\branches\omaha_red_release_branch\
googleclient\omaha\base\registry_monitor_manager.cc @ 547]
0126ffb8 77e6482f 003e744c 00000000 00000000 
goopdate!omaha::Thread::Prepare+0x3f 
[p:\p\agents\hpac3.eem\recipes\164139668\base\branches\omaha_red_release_branch\
googleclient\omaha\base\thread.cc @ 54]
0126ffec 00000000 18011a3c 003e744c 00000000 kernel32!BaseThreadStart+0x34

Original comment by ryanmyers@google.com on 3 Aug 2012 at 6:18

GoogleCodeExporter commented 8 years ago 
That was the only GoogleUpdate.exe process running in ProcessExplorer after I 
got the "unhandled win32 exception occurred in GoogleUpdate.exe" message.

After getting this error regularly for months, I have not seen the error in the 
past few days.

Original comment by brianuc...@gmail.com on 7 Aug 2012 at 11:23

GoogleCodeExporter commented 8 years ago 
I'm getting the same behavior on a regular basis. I recently had to 
reinstall/fix the Microsoft Installer Service after another installer messed 
things up.

I've got Visual Studio 2010 installed. I'll try to generate a dump the next 
time it happens.

-Jody

Original comment by jko...@gmail.com on 30 Oct 2012 at 5:27

GoogleCodeExporter commented 8 years ago 
Jody, that would be great.

I continue to see the error.  My Visual Studio is now registered, but I'm 
unable to generate a dump.  I see the error and am asked if I want to debug 
with VS.  I click Yes.  VS starts, appears to be doing something for a moment, 
and then simply idles saying Solution1.  I'm not very familiar with VS; perhaps 
someone can instruct me further.

Original comment by brianuc...@gmail.com on 1 Nov 2012 at 2:04

GoogleCodeExporter commented 8 years ago 
I suddenly started getting this on 9/3/15 with no new apps installed.
Now Chrome will not work, it hits the windows error and goes into debug see 
attached.
I have searched for options and after multiple reboots and chrome un/re 
installed 
and in the forum they recommended installing canary.  So far I can run canary 
but I need a stable system for my business.

Any help to solve once again another Microsoft mess.

thx
mike

Original comment by mapo...@gmail.com on 4 Sep 2015 at 4:04

Attachments:

GoogleCodeExporter commented 8 years ago 
I am experiencing same error as in #14. Chrome not working at all and wants to 
install Visual Studio. Rebooted multiple times and reinstalled Chrome. Still 
no-go. I use Chrome extensively at work successfully, but this home setup 
doesn't work.

Original comment by niemi.te...@gmail.com on 7 Sep 2015 at 2:45

GoogleCodeExporter commented 8 years ago 
I am having the same problem as #15, my chrome just suddenly started not 
working. An unhandled win32 exception occured in chrome.exe [1068]. It happens 
if I open chrome and also when I try to reinstall chrome I instantly get it. If 
you need something else let me know that might help let me know.

Original comment by cliffman...@gmail.com on 15 Sep 2015 at 3:17