Databases
StackOverflow2013
Postsdbo
POFail to load NPAPI plugin in Google Chrome on Mac OS X
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POFail to load NPAPI plugin in Google Chrome on Mac OS X
    text
    copied!<p>I have been trying to get Google Chrome (6.0.401.1 dev) on Mac OS X to load an NPAPI plugin without success so far. I have been working around the npsimple example from here: <a href="http://git.webvm.net/?p=npsimple" rel="nofollow noreferrer">http://git.webvm.net/?p=npsimple</a>.</p> <p>Using gcc on Mac and VC++ 2008 on Windows I managed to get it running on Safari and Firefox on Mac OS X and Firefox and Google Chrome on Windows, but not on Google Chrome on Mac OS X.</p> <p>When trying to debug Google Chrome on Mac OS X it seemed Google Chrome was briefly dyld-loading (and immediately dyld-unloading) the plugin on startup, but without actually looking-up any symbols within the plugin or calling any of the functions. It seemed to be doing that for every plugin, though.</p> <p>Also, when loading a page with the embed-tag for the plugin, Google Chrome did not seem to even dyld-load the plugin and no functions were called (not even NP_GetEntryPoints). Google Chrome also does not output any error message, it just simply does not load the plugin. I am not sure I caught everything with gdb because of Google Chrome using different processes, but I have also tried all the switches like <code>--no-sandbox</code>, <code>--single-process</code> and <code>--plugin-startup-dialog</code> (which incidentally does not seem to work at all on Mac OS X). I also made sure the architecture of the binary matches (i.e. 32-bit for Google Chrome).</p> <p>Has anybody had similar problems before? Is there anything I am missing here, like a gcc switch when compiling or something?</p> <p>Any help would be greatly appreciated.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload