Philafilly/malpaso,

I'm truely sorry for the inconvenience. I can understand how you feel that us saying it's Google issue to correct is just passing the buck or pointing fingers at someone else. However, it's actually the truth that it's a Chrome issue. We've researched the issue from our end and the issue lies within the Google Chrome code falsely stating that the Norton Confidential plugin has crashed. This is a timing issue in Google Chrome that they need to adjust. Because this exists outside of our codebase, we don't have any workarounds or solutions. We're unfortunately at the mercy of Google's effort to fix this issue in Chrome. 

If you look at the bug report we submitted to Google, you'll see that we actually reported this issue to them back in August: http://code.google.com/p/chromium/issues/detail?id=92374

We're very active in trying to get this issue resolved, and hope it will be soon. Unfortunately, the ball is in Google's court on when they will address this. I would suggest clicking the "Star" icon on the top-left of the page I linked to above to subscribe to the Google defect report. Hopefully that will help them see the strong interest in getting this issue corrected.