Plugins/OOPP Branch Tracking

This page is intended to track all the landings that occurred as a result of OOPP in mozilla-central. This is necessary in order to know exactly what needs to be backported to mozilla-1.9.2.

• initial merge: revision 8ef83d174df3
• WinMo fixup: cac067156b24
• build/merge fixup: 7cf183f21651
• SeaMonkey configure fixup: 848a7cf64d03
• Windows --disable-ipc bustage: 566979627622
• Mac won't load any plugins: 93c3fee6ec69
• jsreftests suddenly started working: 9f7c1fa9b2de and then 3b4baf256382
• fix static builds SM/TB: 60937d3bcc2a
• Build layout-debug with libxul: 925595f3c086
• nsTraceRefcntImpl.cpp bustage on Solaris: 4fa4c6639e28
• Merge from e10s: 4eef63c0c6c9
• Merge from e10s: 3b4baf256382
• NPBool is actually word-sized sometimes: 4f1faaaa0388
• crash in nsObjectFrame::IsOpaque: 1eb1763c6540
• bug 531821 - add licenses related to Electrolysis: b2b5f07a77ea
• re-enable test_crashing.html: 1cb8d8078bc5
• bug 534736 - crash within mozilla::plugins::PPluginInstanceParent::DstroySubtree: 0ed8211f4e54
• bug 535298 - IPDL unit test for use-after-free crashed in RPC: 8f9b7035a216
• bug 535298 - Cancel the NotifyMaybeChannelError event if the AsyncChannel is destroyed: 9bf1d7da878f
• bug 535802 - Disable the Windows JIT crash dialog when running mochitests: c63aea2f8c16
  • followup for Linux bustage: 6e9b8529e66b
• bug 535867 - Threadsafety problem causing tinderbox crash: 1ad5a1b5963a
• bug 535298 - Test crashes which occur during NPP_New or NPP_Destroy: a1598f1a2d70
  • followup: plugin instantiation (and sometimes destruction) is asynchronous: 43061853e246

Also track:

• partial update failure to set mozilla-runtime as executable, bug 535090

Possibly related:

• bug 535357 - idle timer QI correctly: e303c71532e0
• bug 533371 - separate plugintag code from the plugin host: ab5ad57e8eea
• {{bug|535501} - stop storing xpconnect status in the plugin tag: 90c4df5d4ec9
• bug 535660 - plugin instance stopped/started state management: 7b4a0ecd39ff