Confirmed users
1,798
edits
Release Management/WER Investigation: Difference between revisions
Release Management/WER Investigation (view source)
Revision as of 16:13, 24 October 2011
, 24 October 2011→Resources
No edit summary |
|||
| (4 intermediate revisions by the same user not shown) | |||
| Line 21: | Line 21: | ||
* Breakpad design docs - [https://code.google.com/p/google-breakpad/w/list https://code.google.com/p/google-breakpad/w/list] | * Breakpad design docs - [https://code.google.com/p/google-breakpad/w/list https://code.google.com/p/google-breakpad/w/list] | ||
* [https://blogs.msdn.com/themes/blogs/generic/post.aspx?WeblogApp=wer&y=2009&m=03&d=16&WeblogPostName=faq&GroupKeys= FAQ - WER Services] | * [https://blogs.msdn.com/themes/blogs/generic/post.aspx?WeblogApp=wer&y=2009&m=03&d=16&WeblogPostName=faq&GroupKeys= FAQ - WER Services] | ||
* [https://winqual.microsoft.com/help/dp_eventlist.htm WinQual Event List Columns Explanation] | |||
== Builds == | == Builds == | ||
| Line 30: | Line 31: | ||
=== Uploading File Mappings === | === Uploading File Mappings === | ||
* MS suggests using the "Upload File Mappings option" on the Administration menu | * MS suggests using the "Upload File Mappings option" on the Administration menu | ||
* | * Can upload file mappings, but might be out of date: [https://blogs.msdn.com/themes/blogs/generic/post.aspx?WeblogApp=wer&y=2009&m=06&d=12&WeblogPostName=using-the-product-mapping-file-upload-web-service&GroupKeys= blog post] | ||
== WinQual Update Frequency == | == WinQual Update Frequency == | ||
* "By default we collect 10 cab (minidump) files per event" | |||
* Lag times | * Lag times | ||
** "Once we receive cab files for an event you will generally be able to see these cabs within a few hours of us receiving them." | ** "Once we receive cab files for an event you will generally be able to see these cabs within a few hours of us receiving them." | ||
| Line 59: | Line 60: | ||
** (?) Can we make use of individual hit event info in general? (as opposed to just crash cabs) | ** (?) Can we make use of individual hit event info in general? (as opposed to just crash cabs) | ||
* (?) Will hangs (heap dumps) need to be handled any differently than minidumps? | * (?) Will hangs (heap dumps) need to be handled any differently than minidumps? | ||
** Hang blog posts: [https://blogs.msdn.com/themes/blogs/generic/post.aspx?WeblogApp=wer&y=2009&m=03&d=19&WeblogPostName=let-there-be-hangs-part-3-the-hungapp-module&GroupKeys= part 3] and [https://blogs.msdn.com/themes/blogs/generic/post.aspx?WeblogApp=wer&y=2009&m=03&d=19&WeblogPostName=let-there-be-hangs-part-4-better-bucketing-in-windows-vista&GroupKeys= part 4] | |||
** They are bucketed differently. On XP, "hangs really only have 2 effective bucketing parameters... all of particular version of an application’s hangs ended up in a single bucket." On Vista it's better, but "there are still edge cases (just as there are in crash bucketing) where a bucket does not uniquely identify a single bug." (^^ see blog posts) | |||
** Need to also understand how to represent [https://blogs.msdn.com/themes/blogs/generic/post.aspx?WeblogApp=wer&y=2010&m=08&d=16&WeblogPostName=xproc-application-hang-cabs-in-windows-7&GroupKeys= cross process hangs] | |||
* (?) Who do we give access to minidumps? | * (?) Who do we give access to minidumps? | ||
* (?) What is our current data retention policy? | * (?) What is our current data retention policy? | ||