Recently we noticed that when users of our site would open multiple video pages from a search page of links (say for example, more than three to six), some of the group would not load the plugin and would resort back to the default player, even going so far as to ignore the params in the config.xml file. Initially we thought it was the plugin, until we discovered that the plugin wasn't even loading at all in these cases.
We then compiled our own version of the player and added in a ton of Logger calls to see what was going on. In short what we found was that the method loadPlugins in PlayerSetup was failing to send anything associated with the _model instance to the PluginLoader class.
Have you heard of this before and what could possibly be the cause? Would the size of the custom plugin we built have anything to do with this? Currently, our plugin is around 100k. If we were to load a dozen pages one right after another but waiting until each page fully loaded before starting the next one, then everything loads as expected.
If you (or any user) could point us in the right direction, it would be most helpful. As with our site, the above behavior is quite expected.
@MacGeek -
One more debugging step I'd try. First, set up a page which contains nothing but the JW Player (jwplayer.js and player.swf), configured to load your plugin and config.xml. Using a web debugging proxy (we use one called Charles), log the network traffic as you open the page in multiple tabs, and make sure every asset is requested the same number of times as number of page loads. This will provide a baseline and a reproducible test case.