JavaScript Runtime Errors in init.debug.js

Question

I have a custom branding solution for a SharePoint 2013 site collection in Visual Studio.  When I navigate the site collection or debug the solution, I seemingly randomly get Unhandled Exceptions in the /_layouts/15/init.debug.js.  It's rather
0x800a03ee-JavaScript runtime error:  Expected ')' or 0x80070005 JavaScript runtime error:  Access is denied.  The first error occurs just navigating the site collection.  The second error occurs when I hover over the name with presence
at the bottom while editing an item.  I haven't edited this script at all, so what can cause this JavaScript that is in the hive to throw exceptions, and what is a good approach to debug it in order to get to the root of the problem?

Answer 1

Thank you for your response. I'm in a SharePoint 2013 development environment using IE10.  When I added the site collection as a trusted site in the local intranet zone in IE 10, I no longer get the JavaScript runtime related to the name of presence
and Access.  When I deploy the solution, I do not get any errors.  But if I debug in Visual Studio, the solution, which is set of features that installs a master page with custom navigation, I get this error when I navigate the site collection: 
Unhandled exception at line 6784, column 13 in layouts/15/init.debug.js?rev=z/JdnR/rlmz5Wvyfz5qrBg==
0x800a03ee - JavaScript runtime error: Expected ')'
The error occurs in NotifyScriptLoadedAndExecuteWaitingJobs in init.debug.js, and the call stack goes back to DeltaManager$_ScriptLoader in start.debug.js and eventually to the browserHandler, ScriptResource.axd.
init.debug.js, correct me if I'm wrong please, is a JavaScript that SharePoint adds during debugging.  If I go in the hive and add that ')' where it breaks, then everything breaks.  Why is this error thrown, and what is the rev parameter at the
end of the query string?
The custom master page in the solution being installed has a line:
<
asp:ScriptManagerid="ScriptManager"runat="server"EnablePageMethods="false"EnablePartialRendering="true"EnableScriptGlobalization="false"EnableScriptLocalization="true"/>
I added ScriptMode="Debug", and the errors occur during debugging.  I changed it to ScriptMode="Release", and still got the same errors.
I'm not sure if and where in the code things are breaking, but I'm having trouble understanding why SharePoint, Visual Studio, and Internet Explorer behave in this manner.