RE: deadlock while flash plugin calls posturlnotify

2012-10-24 Thread LANGLOIS Olivier PIS -EXT
Karl, Here is the call stack: There must be a pollwrapper flipping the MayWait flag to infinite to. Hence on my VM, there is always some event but since on my real hardware I have no input devices, this makes events rarer... Let me clear that last point before opening a new bug. I'll check if

RE: deadlock while flash plugin calls posturlnotify

2012-10-24 Thread LANGLOIS Olivier PIS -EXT
LANGLOIS Olivier writes: > xulrunner: 16.0.1 Is this a regression? i.e. Do you know whether it worked differently in previous versions? Kindof but I'm coming from very far in the past. I'm trying to upgrade from xulrunner-1.9.0.10. There was even no plugin-container in our previous version! T

Re: deadlock while flash plugin calls posturlnotify

2012-10-24 Thread Karl Tomlinson
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

RE: deadlock while flash plugin calls posturlnotify

2012-10-24 Thread LANGLOIS Olivier PIS -EXT
Update: First I made a small mistake: xulrunner: 16.0.1 Now, I can rule out epoll problem as I have the exact same behavior with poll() I have enabled logging and when the posturlnotify works, I see a NPN function being called: -1250400240[8052998]: NPError mozilla::plugins::child::_posturlno