Plugins/OOPP Testing

A guide to test the newly added Out-Of-Process-Plugins in the Mozilla Nightly builds.

Setup

1. Download the latest Trunk build from http://nightly.mozilla.org
   • Note: Must be linux or Windows 32-bit builds
2. After installing the build, verify the following preference value is enabled in about:config dom.ipc.plugins.enabled = true
3. 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.
4. Run your Process monitor of choice. (eg. Task Manager, Process Explorer for Windows, Pioneer Explorer, top command on Linux)

Testing OOPP

1. Test a few popular plugin sites:
   • Youtube
   • Hulu.com
   • Dailymotion
   • Silverlight
   • Play Mafia Wars / Farmville on Facebook
   • Full flash sites like Gotmilk?, Vitamin Water
   • or Pick one of the many Java sites.
2. Look out for:
   • Crashes
   • Hangs
   • 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.

Filing OOPP Bugs

1. Check for bugs
   • Is there a bug listed here already? If so, comment!
   • If not, open one in bugzilla!
   • use 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.

Resources

• List of known bugs
• Initial Testplan Draft (bsmedberg)
• Electrolysis Weekly Updates