JavaScript error increase in Google Chrome v48

Even the best run DevOps teams have a hard time keeping up with all the variables that can impact their applications in production. The wide array of browsers, browser versions, and operating systems makes it impractical to test all combinations. Our Customer Success team ran into a prime example of this recently.

Google released a new version of Chrome last month, version 48. Following the release we’ve noticed an increase in JavaScript errors in a number of our customers’ monitored environments. Notice the jump in JavaScript errors between browser versions in the image below.

JavaScript errors

Users typically upgrade their browser versions at the request of browser vendors. They don’t stop to consider whether or not a new browser version might not be supported by the web applications they use. Because most applications rely on JavaScript frameworks to render the front-end experience, having a lot of JavaScript errors can easily lead to broken functionality.

This is where Dynatrace automated problem-analysis comes in. Dynatrace artificial intelligence shows you what you don’t know, and can’t reasonably anticipate.

In this case, Dynatrace detected a higher number of JavaScript errors than normal. Have a look at the highlighted portion of the timeline that’s tagged with JavaScript error rate increase.

JavaScript errors

Dynatrace tracks browser-type and browser-version information for all detected JavaScript errors and provides a stack trace that makes it easy to understand the cause of errors. For each detected JavaScript error, Dynatrace provides important details like the name of the file in which the JavaScript error occurred, line number, and even the specific method that produced the error.

JavaScript errors

Dynatrace makes reproducing such errors even easier by showing you exactly which user action triggers each error. Errors with the most significant impact are sorted to the top of the list.

JavaScript errors

PS: There are some known issues with Google Chrome version 48. For one, cached objects don’t always load as expected. There are also reported errors related to images and UI elements not sizing correctly due to a CSS loading issue.

Safia is passionate about technology and travelling. As a Technical Customer Advocate at Ruxit, Safia serves as a customer liaison charged with promoting optimal productivity and satisfaction for Ruxit Customers. When she’s not reading or enjoying a nice meal, she’s out exploring the world.