A guide to test the newly added Out-Of-Process-Plugins in the Mozilla Nightly builds.
Week of May 21st: Stable
- Download the latest Trunk build from nightly.mozilla.org
- Note: Must be Linux or Windows 32-bit builds
- After installing the build, verify the following preference value is enabled in about:config dom.ipc.plugins.enabled = true
- Have at least one of the recommended plugins installed (Flash, Java, Quicktime, and Silverlight)
- Note: because Flash 10.1 beta eats crash reports, we want to focus testing on 10.0.
- Run your Process monitor of choice. (eg. Task Manager, Process Explorer for Windows, Pioneer Explorer, top command on Linux)
- Install a few plugins:
- Test a few popular plugin sites:
- Bubblemark demos - Silverlight 1.1, 2, 3 samples.
- Bing Videos
- Silverlight Showcase
- NBC Olympics (Silverlight)
- Play Mafia Wars / Farmville on Facebook
- Note: Best results can be archived when having a big farm with a lot of items on it.
- Shoot some monsters on Quake Live
- Full flash sites: Gotmilk?, Vitamin Water, Grooveshark
- or Pick one of the many Java sites.
- Look out for:
- incorrect display/audio/interaction
- especially on Windows, any feature which may pop up dialog boxes or system prompts (known cause of hangs), or use the window system in unusual ways (full-screen)
- especially interested in crashes which don't trigger the Mozilla crash reporter, especially when they are reproducible.
Plugin Crashed UI
- Verify the Plugin Crashed UI images displayed after crashing, and submitting a report.
- Check the known OOPP bug list first!
- If not, open one in bugzilla!. Apply the following (this is done automatically if you use the link back there):
- select Core::Plugins component
- Add [OOPP] in the title
- Add [OOPPTestday] in the Whiteboard
- Add 478976 to the Blocks: field so it gets picked up in the dependency list.
- Crashed Plugin UI
- Extended List of Plugins
- List of known bugs
- Initial Testplan Draft (bsmedberg)
- Electrolysis Weekly Updates
- Bugs filed during testday
Manually Killing the Runtime Process/Report Submission
If you manually kill the mozilla-runtime process, there is no crash, so it's expected that it says "No report available".
All Flash instances live in a single process. If a particular page causes flash to crash, all the tabs with Flash in them will show the plugin-crash UI. After you submit the report, the other tabs shouldn't have a "please submit report" link any more (because you already submitted it in the first tab).
Related Bugs to OOPP
- Fixed OOPP buglist
Updated on Mar 15th, 2010
- META bug 478976 - (OOPP) Electrolysis + plugins tracking
- BRANCH bug 539055 - (LorentzBeta1) Tracking release of Firefox Lorentz Beta 1 with OOPP
- META, FIXED bug 538910 - Plugins: Need a "plugin crashed" UI
- NEW bug 550293 - Tweak visual style of crash-reporter UI
- NEW bug 550303 - Update crash-reporter UI and tweak visual style
- NEW bug 550293 - plugin-crashed UI needs more user opt-in
Mac OS Versions not supported
- Mac 10.5 will not be supported per bug 571135#c15