08-15-2012 04:16 PM - edited 08-15-2012 04:18 PM
I've seen issues with Norton Confidential (NIS 2012) and Chrome over the past few days ... what seemed like random crashes. I also noticed an odd bug where links were offset by a bit - clicking on another tab and clicking back would resolve it. I've seen Chrome do a few updates, and NIS also did an update last night. Today, the crashes were happening consistently. Also, my Google+ was no longer working ... I could sign in, but clicking almost any links would pop up a "Loading..." message. I'd usually see "Norton Confidential has crashed" on most / all tabs as well.
Google+ was the most annoying issue for me, so I decided to try disabling Norton Confidential in Chrome (as other suggested)... guess what? Google+ is working fine again. So, whatever Google / Symantec / Microsoft are doing with these updates, it made things worse ... at least disabling Norton Confidential seems to be a good workaround. I'd like the added safety, but not if it's going to ruin my entire browsing experience.
Symantec, I hope you get this sorted out soon.
08-15-2012 05:08 PM
I'm new to this issue, but experienced it today for the first time.
My bet is that this issue will never be fixed, because the Symantec / Microsoft / Google relationships are not privy to those outside the companies, and cross-company politics seems suspect.
To my mind, the plugin maker has the obligation to make their plugin work within the host application. And if that is not possible, the plugin maker should make the reasons clear and public. If they don't, they risk the kind of discredit that Symantec is receiving here -- and justifiably so.
08-15-2012 06:35 PM
I switched to Google Chrome from Firefox a few weeks ago due to the issues Firefox has with the Norton toolbar after every update. Today, for the first time, Norton Confidential crashed and took Chrome down with it. The thing I prize most about Norton is the Identity Safe. If I need to delete the toolbar, including Identity Safe, in order to stop the crash, I'm thinking that the problem wasn't the web browsers not working out the problems with Norton before updates, but Norton's inability to cooperate with Google and Mozilla in order to solve issues like this. After all, Norton, it IS your program, so it is your responsibility.
08-15-2012 07:10 PM
I have the same situation - I just started getting the error on the 8th and I don't have Norton Confidential installed that I can see unless it is part of Norton 360.
Some help would be appreciated.
08-15-2012 07:39 PM
08-15-2012 08:25 PM
I only have same problems with norton confidential crash involving google chrome, gmail, internet browser and other mail as allowed to open in AOL. As suggested by virtual support the live update wouldn't open in order to run.
Norton 220.127.116.11 installation today, 8/15/12 around 2pm DST set off these problems as non were occuring prior to then.
Thanks for secure resoultions!
08-15-2012 08:26 PM
I'm aware of the issues related to the update. BUT my point is this very thread, commenting on the crashes, started last September, pre-dating the recent update, thus indicating this is just the latest manifestation of norton confidential crashing.
08-16-2012 05:27 AM
I installed Norton Internet Security 2012 today from disc, and then ran live update.
I have always used the latest version of Internet Explorer as a browser, currently ie9, and have been using Norton Internet Security for many years. I installed a new version from disc because it was cheaper to buy than pay to download the update!
After the live update had finished I tried to log in to www.evony.com to play a game that I have been playing on and off for three years without a problem. Internet Explorer stopped working!
Thinking that it may be a problem with Evony and ie9 I installed google chrome.
Then when attempting to enter the site I get a message saying that Norton Confidential has crashed. I'm wondering if the same problem is affecting ie9 and google chrome?
Been trying to follow a thread relating to Norton Confidential crashing, but it seems to have been happening for quite a while with no apparent resolution!