I sent you the dump file. On a side note, I believe I actually discovered where the problem lies. I had configured Chrome with the -- new-http switch. It was working fine for quite some time and only seemed to pose a problem once the Dev Channel was no longer having the About Google Chrome dialog problem (where it wouldn't show if Chrome was up-to-date and would leave open a chrome.exe after the browser was fully closed.) So I believe the problem lies specifically with --new- http.
I was also using the --magic_browzR switch, but in testing, this switch does not appear to cause any conflict. I only crash with version 0.2.153.1 of Google Chrome (through the Dev Channel) and the -- new-http switch. I hope this helps. Does anyone want to confirm this for me on their own systems? At your own risk, of course. ;) On Sep 26, 8:43 am, "Nicolas Sylvain" <[EMAIL PROTECTED]> wrote: > On 9/26/08, Bob Oliver Bigellow XLII <[EMAIL PROTECTED]> wrote: > > > > > > > Event Type: Warning > > Event Source: Chrome > > Event Category: None > > Event ID: 2 > > Date: 9/26/2008 > > Time: 8:25:23 AM > > User: CEN\SORED > > Computer: CENSORED > > Description: > > The description for Event ID ( 2 ) in Source ( Chrome ) cannot be > > found. The local computer may not have the necessary registry > > information or message DLL files to display messages from a remote > > computer. You may be able to use the /AUXSOURCE= flag to retrieve this > > description; see Help and Support for details. The following > > information is part of the event: Chrome. Crash not uploaded. > > Error=8004fffd.. > > Unfortunately it looks like this crash did not make it to the crash server. > > If you want, you can send me the crash dump manually. It's going to > help me see where the crash is, and see if there is any workaround. > Trying the new profile is a good idea too. > > To send me the crash dump : > > 1) Shut down Google Chrome completely (if it is running). Make sure Chrome > is not running. > > 2) Then go to Start \ Run and type in: > "%USERPROFILE%\Local Settings\Application > Data\Google\Chrome\Application\chrome.exe" --noerrdialogs > > 3) With this new Chrome window, reproduce the browser crash > > 4) Chrome will not pop up the Application Error dialog, but will instead > just disappear on a crash. > > 5) Open Start \ Run and type in %TEMP% (and hit Enter) > > 6) Find the most recent .dmp file in this folder. It will have an ugly name > such as "3ccb9c93-8e2f-4059-8922- > 71d3afd1952c.dmp" but the timestamp should be very recent since it was just > created. Sorting by Data Modified makes it > easy to spot. :) > > 7) Attach the .dmp file to a private email addressed to me > > Please remember to refer to this bug in your email, for quick reference. > > Thanks. > > Nicolas > > > > > On a side note, I do get the whole "don't use the dev channel" > > thing... I knew what I was getting into. Previously, I had actually > > been installing the latest unofficial Chromium builds which is also > > understandably less stable. I'm just an experimenter. I wouldn't die > > if I lost all of my profile stuff. In fact, every since the latest > > version of the Google Toolbar for FireFox has come out, I have been > > itching to use FireFox more. I can't live without the Google Toolbar > > (mainly the notebook integration, the Google Bookmarks integration, > > and the form filler). I would have just kicked myself if I nuked > > everything, started over, got things working, and THEN found out there > > was a way to install a previous version without wiping things out... > > so I thought I'd ask first. Thanks for the response! Hope the info > > above is what you were looking for. I'll try the profile thing next. > > > On Sep 25, 11:41 pm, "Nicolas Sylvain" <[EMAIL PROTECTED]> wrote: > > > > On 9/25/08, Bob Oliver Bigellow XLII <[EMAIL PROTECTED]> wrote: > > > > > So, I subscribed to the Dev Channel. Today, I happened to notice that > > > > the About dialog is working again (it states that Google Chrome is up- > > > > to-date and is at version 0.2.153.1)... this is on a machine at work. > > > > On my machine at home, it also appears to work... HOWEVER... Google > > > > Chrome now crashes every 30-60 seconds or so whether I am doing > > > > anything or not. I can just run the browser, leave it alone (with the > > > > New Tab showing) and in time, it will crash saying WOAH Google Chrome > > > > has crashed (or something to that effect.) > > > > > I am currently using a build of Chromium just to be able to post this. > > > > > Is there any way that I can get to a previous version of Chrome > > > > without losing any of my settings, saved passwords, etc? > > > > > I have tried re-installing Chrome... I also set myself back to the > > > > Beta Channel... and each time it appears to install, but is still at > > > > version 0.2.153.1 and still has the problem. I fear that first doing > > > > an install will hose my settings or my stored passwords, etc... > > > > > Please advise. > > > > It would be good to have a call stack of the crash. Can you check in > > > the event viewer, under Application, to see if you have events coming > > > from "Chrome". If yes, there must be a crash id. > > > > This is possibly a profile corruption. If you think your stored > > > passwords and settings are really important, I suggest that you don't > > > use the Dev channel, it is not as tested as a real released build and > > > corruptions like this are more likely to happen. > > > > Can you try to launch chrome with an alternate profile to see if it's > > > the problem. You can use "chrome.exe > > > --user-data-dir=C:\Path\To\Alternate\Profile" to do this. > > > > Nicolas > > > > > On Sep 16, 12:32 am, Mark Larson <[EMAIL PROTECTED]> wrote: > > > > > Google Chrome now provides a way for people to get early access > > releases > > > > > automatically: the Dev channel. > > > > > > The Dev channel lets you test the latest fixes and get access to new > > > > > features as they're being developed. We will release new builds to > > the Dev > > > > > channel about every week so that you can preview --and provide > > feedback on-- > > > > > what's coming in Google Chrome. > > > > > > If you want an easy way to help make Google Chrome better, want to > > test new > > > > > changes with your website before they're released generally, or > > just like > > > > > being on the bleeding edge, please sign up for the Dev channel. > > > > > > You can learn more about the Dev channel and how to subscribe > > here:http://dev.chromium.org/getting-involved/dev-channel/ > > > > > > We just released 0.2.152.1 to the Dev channel. The release notes are > > here:http://sites.google.com/a/chromium.org/dev/getting-involved/dev-chann... > > > > > > If you have any questions, please send them directly to me (so I > > can compile > > > > > the FAQ). > > > > > > Thanks, > > > > > Mark Larson > > > > > Google Chrome Program Manager --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
