PPAPI: Add unlocking for PPP calls and callbacks. Add more locking.

ppapi/proxy/ppb_message_loop_proxy.cc

Index: ppapi/proxy/ppb_message_loop_proxy.cc
diff --git a/ppapi/proxy/ppb_message_loop_proxy.cc b/ppapi/proxy/ppb_message_loop_proxy.cc
index 927e42f3118364cd3b35064052fec153186e6bf0..24aea15e7e6a48fb2e670c1c745f16573e42d54f 100644
--- a/ppapi/proxy/ppb_message_loop_proxy.cc
+++ b/ppapi/proxy/ppb_message_loop_proxy.cc
@@ -197,8 +197,9 @@ void MessageLoopResource::PostClosure(
     const base::Closure& closure,
     int64 delay_ms) {
   if (loop_.get()) {
-    loop_->PostDelayedTask(
-        from_here, closure, base::TimeDelta::FromMilliseconds(delay_ms));
+    loop_->PostDelayedTask(from_here,
+                           RunWhileLocked(closure),

[brettw, 2012/02/13 20:52:34]

Isn't this closure into user code, where we would want to be unlocked?

[dmichael (off chromium), 2012/02/13 21:15:33]

Yes, thank you, nice catch. I added a comment to PostClosure that it doesn't
acquire the lock, to hopefully prevent somebody using it to schedule proxy
operations. Currently PostQuit uses it too, but that doesn't need to grab the
lock either.

+                           base::TimeDelta::FromMilliseconds(delay_ms));
   } else {
     TaskInfo info;
     info.from_here = FROM_HERE;