Can you explain what sequence actions you took to generate that output? Here is what you need to do to cause a plugin to reload: 1) Reload the extension. 2) Reload the page that is hosting the plugin.
On Wed, Nov 4, 2009 at 1:18 PM, Jean-Lou Dupont <jeanlou.dup...@gmail.com>wrote: > > I am trying to figure out what would be a repeatable pattern but it > definitely seems that Chrome gets confused after a series of disable/ > reload actions on an extension which contains an NPAPI plugin. Most > annoying. > > npapi-dbus[20669]: Library loaded > npapi-dbus[20669]: NP_GetValue, variable: 1 > npapi-dbus[20669]: NP_GetValue, variable: 2 > npapi-dbus[20669]: **** Library being un-loaded **** > > There should be a log entry with "Library loaded" and a continuation > of messages but nothing happens anymore. Note that the "Library > loaded / unloaded" messages are generated through a syslog call when a > global static object gets created/destroyed. In other words, my "main > plugin logic" doesn't not interfere at this point. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to chromium-extensions@googlegroups.com To unsubscribe from this group, send email to chromium-extensions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en -~----------~----~----~----~------~----~------~--~---
