I've noticed this as well, but there's no rhyme or reason besides "go to a web page, watch entire browser crash". There doesn't seem to be any way to repro it or repeat it, nor does the specific page seem to matter.
Unfortunately I'm running continuous builds which don't have breakpad, so I'm not able to see a stack. Just wanted to say I have seen a drastic increase in crashes so we should be on the lookout and probably expect higher crash reports in 203 if/when it goes out. On Sat, Aug 29, 2009 at 11:53 PM, Gobbledegook<[email protected]> wrote: > > Thanks for that. > > I will try and reproduce it and get back to you. > > On Aug 30, 2:27 am, Jim Roskind <[email protected]> wrote: >> In answer to your "what would constitute a good bug report?" >> At a minimum, add any plausibly significant details. For instance, rather >> than saying "I'm browsing the same site as I do every day," consider saying >> what site you are browsing, or possibly, list the exact URL sequence you go >> through (especially if the cause is entirely reproducible). if you can't >> repro it, try to talk about what it is that you are doing, explicitly. Do >> you start with 1 tab open, or 40? What are some/all of the tabs?? What is >> the site that seems to induce the crash? What sort of things are you doing >> on that site? Reading a certain set of blogs? Reading articles? Posting? >> etc. >> >> The best bug report is a completely reproducible set of actions. >> >> The worst bug report doesn't give a clue as to what the user was doing near >> the bug event. >> >> You want to be as close as possible to the first. Anything that gives a >> tester a shot at tickling the bug is a giant step toward a bug getting >> attention, and getting fixed asap. Sometimes we see a common thread among a >> pile of bugs... and that gives us a clue. ...but we need some threads to >> consider ;-). >> >> Thanks in advance, >> >> Jim >> >> >> >> On Sat, Aug 29, 2009 at 3:37 PM, Gobbledegook <[email protected]> wrote: >> >> > so far so good. >> >> > so if i'm browsing the same site i browse everyday, and suddently >> > chrome starts dunking, and i want to file a bug report, what would >> > constitute a good report? >> >> > On Aug 29, 11:24 pm, Marc-Antoine Ruel <[email protected]> wrote: >> > > We do look at bug reports; higher quality reports (with facts and >> > > context) will be triaged faster. >> >> > > M-A >> >> > > On Sat, Aug 29, 2009 at 6:19 PM, Gobbledegook<[email protected]> >> > wrote: >> >> > > > thanks. i'll give that a spin. >> >> > > > no one ever seems to repsond on crbug.com so this is just an amazing >> > > > place to come for debugging and instant advice. >> >> > > > On Aug 29, 11:17 pm, Marc-Antoine Ruel <[email protected]> wrote: >> > > >> Still, we are getting a lot of sqlite3 crashes in this revision, you >> > > >> may want to start with --user-data-dir=c:\test to see if it fixes the >> > > >> problem. >> >> > > >> M-A >> >> > > >> On Sat, Aug 29, 2009 at 6:11 PM, Peter Kasting<[email protected]> >> > wrote: >> > > >> > On Sat, Aug 29, 2009 at 2:58 PM, Gobbledegook < >> > [email protected]> wrote: >> >> > > >> >> every 10 minutes i'm getting one crash. It was rock solid till >> > earlier >> > > >> >> today. >> >> > > >> > Don't send this to chromium-dev. File bugs at crbug.com. >> > > >> > PK > > > -- Mike Pinkerton Mac Weenie [email protected] --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
