Plugins/OOPP Testing

From MozillaWiki
Jump to navigation Jump to search

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

Today's Status

As of February 16th:

  • Nightly builds are once again generated on Windows.
  • There's still a problem whereby killing the mozilla-runtime process will not trigger the new crash UI in some instances.

Setup

  1. Download the latest Trunk build from http://nightly.mozilla.org
  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. Install a few plugins:
  2. Test a few popular plugin sites:
  3. 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.

OOPP Bugs!

  1. Check the known OOPP bug list first!
  2. 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.

Resources

Retrieved from "https://wiki.allizom.org/index.php?title=Plugins/OOPP_Testing&oldid=206040"