Release Management/WER Investigation: Difference between revisions

Jump to navigation Jump to search

Release Management/WER Investigation (view source)

Revision as of 19:57, 6 October 2011

1,511 bytes added ,  6 October 2011
no edit summary
No edit summary
Line 1: Line 1:
This page will track the initial investigation of Windows Error Reporting (WER). Our current plan is to hook our bug tracking and metrics into [https://winqual.microsoft.com/ Winqual], the site/webAPI used to access Microsoft's crash info. Using this info will help diagnose hangs (which aren't currently tracked) on Windows XP and later, and may even uncover new crashes.
This page will track the initial investigation of Windows Error Reporting (WER). Our current plan is to hook our bug tracking and metrics into [https://winqual.microsoft.com/ Winqual], the site/webAPI used to access Microsoft's crash info. Using this info will help diagnose hangs (which aren't currently tracked) on Windows XP and later, and may even uncover new crashes.
== Areas of Interest ==
* Terms associated with using Winqual (data after 6mos, etc.)
* Creating a library/service to act as a
** Sync layer between Winqual and our crash storage service
** Method of providing symbols/app version/file mappings for new builds
** Auto-filer for [[Bugzilla]], possibly dealing with dupes
** Provider for [[Socorro]] crash metrics
* Applicability for other platforms such as Mac OS X


== Associated Bugs ==
== Associated Bugs ==
Line 17: Line 8:
* Short description on MSDN: [http://msdn.microsoft.com/en-us/windows/hardware/gg487440 WER: Getting Started]
* Short description on MSDN: [http://msdn.microsoft.com/en-us/windows/hardware/gg487440 WER: Getting Started]
* Longer guide (more targeted at hw/drivers though): [https://winqual.microsoft.com/help/developers_guide_to_wer.htm Developers Guide to WER]
* Longer guide (more targeted at hw/drivers though): [https://winqual.microsoft.com/help/developers_guide_to_wer.htm Developers Guide to WER]
* [http://winqual.microsoft.com/help/winqual_help.pdf Full WinQual Docs]
* Microsoft's WER client: [http://stackhash.codeplex.com/ Stackhash]
* Microsoft's WER client: [http://stackhash.codeplex.com/ Stackhash]
* API documentation: [http://stackhash.codeplex.com/SourceControl/list/changesets# StackHash source download] > 3rdparty > WinQual API > Data Services.docx
* [https://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032286008&EventCategory=5&culture=en-US&CountryCode=US MSDN Webcast: Getting Started with Windows Error Reporting] (video from 2006)


== Needed for Investigation  ==
== Needed for Investigation  ==
*<strike>VMWare/Windows 7 ({{bug|690490}} &amp; {{bug|690491}})</strike>
*<strike>VMWare/Windows 7 ({{bug|690490}} &amp; {{bug|690491}})</strike>
*<strike>Winqual account</strike>
*<strike>Winqual account</strike>


== Questions that need Answering ==
== Builds ==
* What needs to be done to creating the file mapping XML files from each build?
=== Creating File Mappings ===
* What information is actually provided by Winqual (on the site, in the REST data, and in the CAB files)?
* MS suggests using their Microsoft Product Feedback Mapping Tool (AppMap.exe) to create a file manifest - required for crash collection for a new product version
* How will we symbolicate the crash dumps?
* (?) Need to explore generating this file manifest so that the build machines can create it
** The Developers Guide mentions that "Microsoft encourages people to submit their symbols when they submit drivers to be signed". Can we take advantage of that?
 
* How much overlap is there with current crash tracking at Mozilla?
=== Uploading File Mappings ===
* MS: Will we run into any limits if staying synchronized with the server?
* MS suggests using the "Upload File Mappings option" on the Administration menu
* MS: Any limitations based upon the number of builds (delays, etc). Especially necessary if we decide to track nightlies.
* (?) Need to figure out if the WER web API can instead be used to perform an upload
* How does debugging using minidump files work?
 
** Requires both the associated symbols as well as the associated images.
== WinQual Update Frequency ==
* Crash/hang "buckets" only collect CAB files for the first few instances of the crash - what does that mean for debugging?
* (?) Determine if there are any limitations to the number of products that can be registered (for possible use with nighties
** In the Developers Guide, it mentions "We can collect additional files on request if you find that you need more information for debugging."
** Need to take into consideration the >2 day lag time on getting reports
* (?) Bandwidth limits for pulling down
* Only the first few cab files are stored for a crash. The event viewer web interface offers the ability to make a "Data Request" to collect "Processor & Memory Information", the heap, specific files (logs, etc.), additional cab files
** (?) Can the web API be used to expose this to developers or will we need more accounts?
* (?) Need to find out what it means when no cab files are available and the web interface offers "(click here to switch to collection mode)" - aren't we always collecting?
 
== Accessing WinQual Data ==
=== Windows Live Login ===
* (?) Access in winqual requires a Windows Live login. Similarly, in MS's StackHash client requires the use of Windows Live Sign-in Assistant. Need to determine if the associated library is required for logging in.
* (?) Need to figure out what account we'd use for automated tools
 
=== WER Web API ===
* API documentation: [http://stackhash.codeplex.com/SourceControl/list/changesets# StackHash source download] > 3rdparty > WinQual API > Data Services.docx
 
== Breakpad/Soccoro ==
* (?) Need to understand the overlap between WinQual crash data and Breakpad crash data, map the applicable info, and decide what to do with "additional" info
** (?) 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?
 
=== Cab File Contents (for collector/processor) ===
* WERInternalMetadata.xml - (possibly) not present if version.txt is.
* AppCompat.txt (also all lower) - not present if WERDataCollectionFailure.txt is.
* WERDataCollectionFailure.txt - includes error message if processing failed in MS.
* version.txt - only come across this once. Only included OS version.
* For crashes
** ______.{m}dmp - minidump file. These types of dumps already appeared to be handled according to http://code.google.com/p/google-breakpad/wiki/ProcessorDesign
* For hangs
** <process-name>.xml -  
** memory.hdmp - info about the difference between a heapdump and a minidump [http://msdn.microsoft.com/en-us/library/windows/desktop/bb513622%28v=vs.85%29.aspx outlined here]


== Future Investigations ==
== Future Investigations ==
* Consider providing a solution (link) when the user is presented with the Windows crash dialog
* Consider providing a solution (link) when the user is presented with the Windows crash dialog
** Can even link to an exe (if part of the "Designed for Windows" logo program), which may be a good idea for last ditch effort if even Firefox's safe mode fails (application files no longer pristine, need reinstall).
** Can even link to an exe (if part of the "Designed for Windows" logo program), which may be a good idea for last ditch effort if even Firefox's safe mode fails (application files no longer pristine, need reinstall).
Akeybl
Confirmed users
1,798

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/355908"

Navigation menu