• 0

JS error handling in edge problems


Question

Anyone do JS dev on edge? I have a site that is using extensive AJAX and JS / jQuery / etc

 

The site has a global error handler set up on window.onerror (only to catch unhandled exceptions and log them on the server via posting the error detail back as a json package) which works perfectly fine in IE11, Chrome, FF, Safari, but when I do the same exact thing in Edge, if the function executed in JS has an error its like the function just will not run. to test this I set up just a junk function and called it with a button press, <button onclick = "testfunc(this);"> pretty simple, put into that function some code that just says 

 

function testfunc(button) {

throw new Error('test');

}

 

simple right? In Chrome, IE11, Safari, FF I get my error handler with that error message...

 

in Edge, that function doesn't even start to execute... remove the throw new error and put in a junk call like foo(); which is an undefined function same result.... replace that with alert('hello?'); and boom executes.....

 

JS isn't my primary language (actually never used it much until recently, was primary a back-end coder before) so am I missing something, doing something wrong? what? Or is something different with the Edge JS engine?

Link to comment
https://www.neowin.net/forum/topic/1303094-js-error-handling-in-edge-problems/
Share on other sites

5 answers to this question

Recommended Posts

  • 0
  On 18/07/2016 at 14:53, neufuse said:

no one?

Expand  

I setup the following code on a test.html page and ran it on IE Edge and the alert is showing up just fine for me - 

 

<script type="text/javaScript">

window.onerror = function(message, source, lineno, colno, error)
{
	alert(message + ": " + source + " : " + lineno + " : " + colno + ": " + error);
}

function testfunc(button) {
	throw new Error('test');
}
</script>

<button onclick="testfunc(this);">Test</button>

 

  • 0
  On 24/07/2016 at 04:25, svnO.o said:

I setup the following code on a test.html page and ran it on IE Edge and the alert is showing up just fine for me - 

 

<script type="text/javaScript">

window.onerror = function(message, source, lineno, colno, error)
{
	alert(message + ": " + source + " : " + lineno + " : " + colno + ": " + error);
}

function testfunc(button) {
	throw new Error('test');
}
</script>

<button onclick="testfunc(this);">Test</button>

 

Expand  

copied and pasted that into a local html file..... same problem..... testfunc will not execute *scratches head* maybe it's the build I'm on

  • 0
  On 26/07/2016 at 02:23, neufuse said:

copied and pasted that into a local html file..... same problem..... testfunc will not execute *scratches head* maybe it's the build I'm on

Expand  

If it helps, I tested on Edge 25.10586.0.0 / EdgeHTML 13.10586 - other than that maybe some odd browser setting? I'd not worry too much though if its working in the other browsers as well as in the Edge browser version I tried.

  • 0
  On 26/07/2016 at 04:15, svnO.o said:

If it helps, I tested on Edge 25.10586.0.0 / EdgeHTML 13.10586 - other than that maybe some odd browser setting? I'd not worry too much though if its working in the other browsers as well as in the Edge browser version I tried.

Expand  

I just find it odd that the function wont even enter... I could put an alert('test'); before the throw new error and set a break point on it, never enters...

 

remove the throw new error do the same thing and boom alert executes... just very odd, you would think it would at least enter the function

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Only if it's the fastest to open ads and blow up my vision with advertising that I don't want to see. Damn Google
    • Chrome is now faster than ever and Google explains how it did it by Sayan Sen Back in June last year, Google touted some great performance improvements for Chrome and shared a blog post explaining in detail how it managed to achieve them. Today, almost exactly a year later, the search giant is back again with another such post as it continues to make performance gains in its Chromium browser. Interestingly, Google is not the only one to make such claims in recent times. Microsoft also highlighted recently how Edge was getting significantly faster. Both Microsoft and Google have cited the Speedometer 3.0 benchmark to test. We recently measured browsing performance during our T-Force DDR5-7200 RAM review, also using Speedometer 3.0. In its blog post, Google says that the development team made significant improvements to memory management and caching. This includes some redesigning effort of the memory layouts for many internal data structures used in components such as DOM, CSS, layout, and painting. Google says that Blink, the rendering engine in Chromium, now "avoids a lot of useless churn" so as to make better use of the CPU caches. In the areas where memory handling previously relied on garbage collection in Oilpan, like the DOM (document object model), the team has expanded that by shifting from using malloc (memory allocation function) to Oilpan entirely. For those wondering, Olipan is the garbage collector in Blink. Some of the memory management and caching improvements Google made are fundamental to good code optimization. If you recall, recently, a senior Microsoft engineer also pointed out many of these issues in apps that slow Windows down. There are also improvements in handling strings within the renderer; the hashing method was updated to rapidhash, which is said to improve performance. For when rendering tasks become inherently expensive, such as computing CSS styles for various elements, Google adds that caching techniques have been enhanced to achieve higher cache hits and fewer misses.
    • Laptop users, this appears to be single-sided so it should fit even in cases with thin slots.
    • Apple wouldn't be what it is today without China either...
  • Recent Achievements

    • First Post
      Uranus_enjoyer earned a badge
      First Post
    • Week One Done
      Uranus_enjoyer earned a badge
      Week One Done
    • Week One Done
      jfam earned a badge
      Week One Done
    • First Post
      survivor303 earned a badge
      First Post
    • Week One Done
      CHUNWEI earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      428
    2. 2
      +FloatingFatMan
      196
    3. 3
      snowy owl
      191
    4. 4
      ATLien_0
      186
    5. 5
      Xenon
      141
  • Tell a friend

    Love Neowin? Tell a friend!