NortonInternetSecurityBF Keeps Crashing

Today I've uninstalled and reinstalled Norton Internet Security for Mac.  The same issue has just occurred when I had four tabs open in Firefox: coursera.org, google advanced search and two tabs at http://www.imdb.com.

As I said before, I can't observe any pattern that could help you to find the problem.

Unfortunately we have had this unsolved issue for almost 4 months.

Hi Neyserrao,

 

We are working on fixing this issue.  In the mean time can you please do the following and attach some of the crash logs here.

 

1.  Launch Terminal application from /Applications/Utilities/Terminal.app

2.  Copy and paste the below command in terminal and press enter/return.

MOZ_CRASHREPORTER_DISABLE=1 /Applications/Firefox.app/Contents/MacOS/firefox-bin

3.  Browser the websites which can probably crash.

4.  When a crash occurs a new crash log will be created at ~/Library/Logs/DiagnosticReports/ with the name begining plugin-container.

5.  Attach 3 or 4 crash logs in the forum.

Hi, Haridharan!

Thank you for the hint.

I will follow your instructions and as soon as I have a few logs I´ll post it.

Regards,

Ney

Dear Haridharan

 

I'm attaching a pdf with 10 crash reports for you. I have plenty more if you want. It would really be nice if this problem was given some priority, which it evidently isn't at the moment.

 

<script id="ncoEventScript" type="text/javascript">// function DOMContentLoaded(browserID, tabId, isTop, url) { var object = document.getElementById("cosymantecnisbfw"); if(null != object) { object.DOMContentLoaded(browserID, tabId, isTop, url);} }; function Nav(BrowserID, TabID, isTop, isBool, url) { var object = document.getElementById("cosymantecnisbfw"); if(null != object) object.Nav(BrowserID, TabID, isTop, isBool, url); }; function NavigateComplete(BrowserID, TabID, isTop, url) { var object = document.getElementById("cosymantecnisbfw"); if(null != object) object.NavigateComplete(BrowserID, TabID, isTop, url); } function Submit(browserID, tabID, target, url) { var object = document.getElementById("cosymantecnisbfw"); if(null != object) object.Submit(browserID, tabID, target, url); }; // </script>

Sorry, ignore the file "Crash Reports 1-10" if you want more crash reports and go for "Crash Reports 1-12" instead. Only just realised "Crash Reports 1-12" managed to attached after initially being bounced for being too large even though it was right on the 2mb limit.

<script id="ncoEventScript" type="text/javascript">// function DOMContentLoaded(browserID, tabId, isTop, url) { var object = document.getElementById("cosymantecnisbfw"); if(null != object) { object.DOMContentLoaded(browserID, tabId, isTop, url);} }; function Nav(BrowserID, TabID, isTop, isBool, url) { var object = document.getElementById("cosymantecnisbfw"); if(null != object) object.Nav(BrowserID, TabID, isTop, isBool, url); }; function NavigateComplete(BrowserID, TabID, isTop, url) { var object = document.getElementById("cosymantecnisbfw"); if(null != object) object.NavigateComplete(BrowserID, TabID, isTop, url); } function Submit(browserID, tabID, target, url) { var object = document.getElementById("cosymantecnisbfw"); if(null != object) object.Submit(browserID, tabID, target, url); }; // </script>

Hi, Haridharan,

Please find attached one crash report obtained exactly as suggested in your message dated Mar 10th.

Regards,

Ney

Thank you very much for the logs.  We consider this as a high priority and working on a fix.

I don't know if this can help, but it seems (although I'm not sure that all crashes were this way) that, after I reinstalled NIS, crashes occur when I close a tab (Cmd + W).

All the best,

Ney

<script id="ncoEventScript" type="text/javascript">// function DOMContentLoaded(browserID, tabId, isTop, url) { var object = document.getElementById("cosymantecnisbfw"); if(null != object) { object.DOMContentLoaded(browserID, tabId, isTop, url);} }; function Nav(BrowserID, TabID, isTop, isBool, url) { var object = document.getElementById("cosymantecnisbfw"); if(null != object) object.Nav(BrowserID, TabID, isTop, isBool, url); }; function NavigateComplete(BrowserID, TabID, isTop, url) { var object = document.getElementById("cosymantecnisbfw"); if(null != object) object.NavigateComplete(BrowserID, TabID, isTop, url); } function Submit(browserID, tabID, target, url) { var object = document.getElementById("cosymantecnisbfw"); if(null != object) object.Submit(browserID, tabID, target, url); }; // </script>

Hello, Haridharan!

Please find attached one more crash log.

Regards,

Ney

 

I'm having the same issue I've had some time ago: "file type doesn't match file extension" (or something like this).

I'll send you the file by email.

 

<script id="ncoEventScript" type="text/javascript">// function DOMContentLoaded(browserID, tabId, isTop, url) { var object = document.getElementById("cosymantecnisbfw"); if(null != object) { object.DOMContentLoaded(browserID, tabId, isTop, url);} }; function Nav(BrowserID, TabID, isTop, isBool, url) { var object = document.getElementById("cosymantecnisbfw"); if(null != object) object.Nav(BrowserID, TabID, isTop, isBool, url); }; function NavigateComplete(BrowserID, TabID, isTop, url) { var object = document.getElementById("cosymantecnisbfw"); if(null != object) object.NavigateComplete(BrowserID, TabID, isTop, url); } function Submit(browserID, tabID, target, url) { var object = document.getElementById("cosymantecnisbfw"); if(null != object) object.Submit(browserID, tabID, target, url); }; // </script>

<script id="ncoEventScript" type="text/javascript">//

function DOMContentLoaded(browserID, tabId, isTop, url) { var object = document.getElementById("cosymantecnisbfw"); if(null != object) { object.DOMContentLoaded(browserID, tabId, isTop, url);} }; function Nav(BrowserID, TabID, isTop, isBool, url) { var object = document.getElementById("cosymantecnisbfw"); if(null != object) object.Nav(BrowserID, TabID, isTop, isBool, url); }; function NavigateComplete(BrowserID, TabID, isTop, url) { var object = document.getElementById("cosymantecnisbfw"); if(null != object) object.NavigateComplete(BrowserID, TabID, isTop, url); } function Submit(browserID, tabID, target, url) { var object = document.getElementById("cosymantecnisbfw"); if(null != object) object.Submit(browserID, tabID, target, url); }; //

</script>

<script id="ncoEventScript" type="text/javascript">// function DOMContentLoaded(browserID, tabId, isTop, url) { var object = document.getElementById("cosymantecnisbfw"); if(null != object) { object.DOMContentLoaded(browserID, tabId, isTop, url);} }; function Nav(BrowserID, TabID, isTop, isBool, url) { var object = document.getElementById("cosymantecnisbfw"); if(null != object) object.Nav(BrowserID, TabID, isTop, isBool, url); }; function NavigateComplete(BrowserID, TabID, isTop, url) { var object = document.getElementById("cosymantecnisbfw"); if(null != object) object.NavigateComplete(BrowserID, TabID, isTop, url); } function Submit(browserID, tabID, target, url) { var object = document.getElementById("cosymantecnisbfw"); if(null != object) object.Submit(browserID, tabID, target, url); }; // </script>

Hi, Haridharan

Please find attached another crash log file.

Today I noticed that when I sign out from my webmail (globo.com) I get a crash.  This used to happen from time to time, but today I observed the crash every time.

I hope this can help to find the cause of this annoying issue.

Regards,

Ney

<script id="ncoEventScript" type="text/javascript">// function DOMContentLoaded(browserID, tabId, isTop, url) { var object = document.getElementById("cosymantecnisbfw"); if(null != object) { object.DOMContentLoaded(browserID, tabId, isTop, url);} }; function Nav(BrowserID, TabID, isTop, isBool, url) { var object = document.getElementById("cosymantecnisbfw"); if(null != object) object.Nav(BrowserID, TabID, isTop, isBool, url); }; function NavigateComplete(BrowserID, TabID, isTop, url) { var object = document.getElementById("cosymantecnisbfw"); if(null != object) object.NavigateComplete(BrowserID, TabID, isTop, url); } function Submit(browserID, tabID, target, url) { var object = document.getElementById("cosymantecnisbfw"); if(null != object) object.Submit(browserID, tabID, target, url); }; // </script>

Thanks Ney,

 

The logs you have shared were very useful and we have potentially found the issue.  We are working on the fix/testing and at this moment I can't really say when you can expect the update exactly.  However, it should be available sooner.

Hi, Haridharan,

I'm happy to know that you are closer to fixing this issue and happy too because it seems that I could help you in any way.

I hope to hear good news from you soon.

Best regards,

Ney

Hi, Haridharan

Unfortunately it seems that Symantec team hasn't found a solution for this annoying issue.

Although I believe that Symantec support team is working on this problem, I'm disappointed with the very long time with no solution.

I hope we can have a fix soon.

Best regards,

Ney

What's the update on this? Come on Symantec! This has been going on a long time, and we need your help.  I get the error message, "NortonInternetSecurityBF has crashed" multiple times a day across numerous websites.  I hit report crash almost every time.  Work with Mozilla and FIX this! It makes me want my money back.  VERY annoying!

 

 

Although I know that messages regarding this annoying issue should be posted on this thread, I've opened a new one, in

http://community.norton.com/t5/Norton-for-Mac/NortonInternetSecurity-crashes-in-Firefox/td-p/1134808

to see if someone in Symantec pays attention to this long lasting bug.

I don't know if Symantec support team is not capable of fixing it or if is simply neglecting it.

Whichever the answer, I think it's unacceptable.  That's not the way customers should be treated.

Always suspected this was a low priority issue for Symmantec. Shocking really. Until the issue is picked up by an opinion shaping tech mag or blog, looks like we are stuffed. Not renewing my subscription.

What is with this issue?  I have the same problem on the product I purchased 2 days ago.  It seems as if it is still not solved.  I have read through all the threads dated back to Nov 2013.  This is terrible support.

 

Please is there further progress on resolving this bug?