0

I'm working on an NPAPI based plugin, and have been observing an issue when opening the context menu in Chrome, displaying an error message saying that the page is unresponsive after leaving it open for 30 seconds.

I've observed the same issue with Flash Player 10.3 (which uses NPAPI, 11.x versions uses PPAPI).

Also, this issue only happens with Chrome, and trying to open the context menu when we aren't in the mouse down event takes no action, and no menu gets visible.

Any thoughts?

Thanks, Rodrigo.

Georg Fritzsche
  • 97,545
  • 26
  • 194
  • 236
Rodrigo Rivera
  • 157
  • 1
  • 9

2 Answers2

3

This is simply a bug in Chrome's NPAPI plugin host on OS X.

smorgan
  • 20,228
  • 3
  • 47
  • 55
0

The reason why this happens is that you must not ever block the main thread, and when you have the menu open you're blocking the main thread. Since the main thread is blocked, the plugin doesnt' communicate back to the browser process and the browser process detects it as being frozen.

The only solution I can imagine would be something that lets you do what you need on an alternate thread. Chrome will always display that notice if you block the main thread, no matter what you do.

taxilian
  • 14,229
  • 4
  • 34
  • 73
  • Thanks taxilian. I've already tried that way, but when I do that, the context menu doesn't popup at all. – Rodrigo Rivera Apr 04 '13 at 14:59
  • Sounds like you'll either have to wait for the bug that @smorgan pointed out to be fixed or you'll have to use something other than a context menu :-/ His is the answer, so mark it – taxilian Apr 04 '13 at 20:56