TypeError: b is null caused by ArterySignalR

TypeError: b is null caused by ArterySignalR

26 November 2013

I was having an issue where every time I used a web application I would get a script error TypeError: b is null.

I noticed that the browser was making additional requests.

Timestamp: 26/11/2013 11:04:47
Error: no element found
Source File: http://localhost:50819/eb83125a6f0e42b2a59cb3487537607b/arterySignalR/send?transport=longPolling&connectionToken=AQAAANCMnd8BFdERjHoAwE%2FCl%2BsBAAAAvbc54PiR80CIDH1RHxxQqQAAAAACAAAAAAADZgAAwAAAABAAAACjRngKWEyWJkzHQvOs%2FAEHAAAAAASAAACgAAAAEAAAALlRLNKVNnHjvaOOSUPUoK0oAAAAbLHLA5P%2B2Jm2mvIA%2BUDgjjMMin2IlF%2FbvUJGVbmA3Zl1zhg8sY3EJRQAAABy1tMRvPtxvVpXp%2BdtrCCUe7KMXw%3D%3D&requestUrl=http%3A%2F%2Fsaserver1%2FSmartAgent4%2FPageContainer.aspx%3Fpath%3DWorkflowManagement.ascx&browserName=Firefox
Line: 1

I thought; wtf are these? Dam you AVG Web Browsing component! To my surprise; it wasn’t AVG.

Visual Studio 2013 creates a browser link

MSDN:

Browser Link is just a channel between your Visual Studio IDE and any open browser. This will allow dynamic data exchange between your web application and Visual Studio.

I disabled the Browser Link and things started working.

Browser Link

Tools Visual-Studio