LANGLOIS Olivier writes: > xulrunner: 16.0.1
Is this a regression? i.e. Do you know whether it worked differently in previous versions? > and the plugin-container thread stack is: > > #1 0xb7f9a915 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 > #2 0xb5aa4b5f in PR_WaitCondVar () from /usr/lib/firefox-16.0.1/libnspr4.so > #3 0xb5ec108f in ?? () from /usr/lib/firefox-16.0.1/libxul.so 0x0040408F > (mozilla::CondVar::Wait) > #4 0xb6800bf6 in ?? () from /usr/lib/firefox-16.0.1/libxul.so 0x00D43BF6 > (mozilla::Monitor::Wait) > #5 0xb706e54f in ?? () from /usr/lib/firefox-16.0.1/libxul.so 0x015B154F > (mozilla::ipc::SyncChannel::WaitForNotify) > #6 0xb706b1b0 in ?? () from /usr/lib/firefox-16.0.1/libxul.so 0x015AE1B0 > (mozilla::ipc::RPCChannel::Call) > #7 0xb7162dfd in ?? () from /usr/lib/firefox-16.0.1/libxul.so 0x016A5DFD > (mozilla::plugins::PPluginInstanceChild::CallPStreamNotifyConstructor) > #8 0xb7049c31 in ?? () from /usr/lib/firefox-16.0.1/libxul.so 0x0158CC31 > (mozilla::plugins::child::_posturlnotify) > > This really sounds like a IPC problem. I'll compile the debug version to be > able to enable IPC logging. This process may just be waiting for the parent process to reply. If you can get a stack trace (with symbols) of the parent process, then it may be worth filing a bug. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
