Strategies for reliably causing IE 10&11 to crash? Simulating the phenomenon of "Internet Explorer abruptly closing and reopening the tab"

Question

Strategies for reliably causing IE 10&11 to crash? Simulating the phenomenon of "Internet Explorer abruptly closing and reopening the tab"

Here's an interesting query. Is there a method to consistently trigger this error in Internet Explorer 10 & 11 using Javascript, CSS or HTML?

An issue with this website is forcing Internet Explorer to close and reopen the tab.

I'm not trying to create a harmful website, I just need to replicate a scenario where IE crashes for testing purposes.

Are there any known bugs that could cause this error to occur across all versions of IE?

javascript html css internet-explorer

Answer 1

Answer №1

Short version: @CodingIntrigue's suggestion fixed the issue I was having in Internet Explorer 11

If you encounter a memory leak problem, you can incorporate this code snippet into your HTML logic:

<script type="text/javascript">
    while(true) {}    //stop messing around and crash this window to trigger IE11's default behavior of opening a new one
</script>

Note: My browser window was already struggling with memory issues at this point, making it easy to replicate the error consistently. However, on less complex pages, IE11 may not crash as quickly or reliably.

I was facing a memory leak in IE11 with my JavaScript React web app. To resolve it, I attempted to use window.open for a fresh memory start and planned to close the current window using window.close due to IE11-related memory leaks, following the guidelines mentioned here.

The challenge arose when I couldn't execute window.open within the memory full error callback. The memory constraints prevented it. However, by forcing IE11 to follow its default error flow of reopening the tab, I achieved a similar result. The upcoming code illustrates how I implemented the while loop strategy in this scenario, incorporating unhandled promises handling as well.

window.addEventListener('error', function(e) {                     //respond to errors

    var errorMessage = e && e.message ? e.message.toString() : '',
        errorType = e && e.type ? e.type.toString() : '',
        targetNodeName = e && e.target && e.target.nodeName ? 
        e.target.nodeName.toString().toUpperCase() : '';

    //Additional logic added here based on `errorMessage` and `errorType`
    while(true) {}    //stop messing around and crash this window to open a new one via IE11 default behavior

})


window.addEventListener('unhandledrejection', function(e) {
    //Note - This callback has not been invoked yet
    var errorMessage = e && e.message ? e.message : '';
    console.log('in unhandledrejection callback listener: ' + errorMessage, e);
}, true);       //`, true` sets `useCapture` Boolean

The following snippet demonstrates how you could attempt to fill up the memory (although personally, I didn't manage to make it work due to existing memory limitations). Reference taken from @Jaroslav Tulach's answer. You may need to adjust it further according to your requirements.

function gc(max) {
    var arr = [];
    for (var i = 0; i < max; i++) {
      arr.push(i);
    }
    return arr.length;
}
//Attempt to prompt IE11 garbage collector to run
for (var i = 0; i < 10; i++) {                  // repeat until sufficient:
    gc(Math.pow(2, i));
}

Answer 2

Short version: @CodingIntrigue's suggestion fixed the issue I was having in Internet Explorer 11

If you encounter a memory leak problem, you can incorporate this code snippet into your HTML logic:

<script type="text/javascript">
    while(true) {}    //stop messing around and crash this window to trigger IE11's default behavior of opening a new one
</script>

Note: My browser window was already struggling with memory issues at this point, making it easy to replicate the error consistently. However, on less complex pages, IE11 may not crash as quickly or reliably.

I was facing a memory leak in IE11 with my JavaScript React web app. To resolve it, I attempted to use window.open for a fresh memory start and planned to close the current window using window.close due to IE11-related memory leaks, following the guidelines mentioned here.

The challenge arose when I couldn't execute window.open within the memory full error callback. The memory constraints prevented it. However, by forcing IE11 to follow its default error flow of reopening the tab, I achieved a similar result. The upcoming code illustrates how I implemented the while loop strategy in this scenario, incorporating unhandled promises handling as well.

window.addEventListener('error', function(e) {                     //respond to errors

    var errorMessage = e && e.message ? e.message.toString() : '',
        errorType = e && e.type ? e.type.toString() : '',
        targetNodeName = e && e.target && e.target.nodeName ? 
        e.target.nodeName.toString().toUpperCase() : '';

    //Additional logic added here based on `errorMessage` and `errorType`
    while(true) {}    //stop messing around and crash this window to open a new one via IE11 default behavior

})


window.addEventListener('unhandledrejection', function(e) {
    //Note - This callback has not been invoked yet
    var errorMessage = e && e.message ? e.message : '';
    console.log('in unhandledrejection callback listener: ' + errorMessage, e);
}, true);       //`, true` sets `useCapture` Boolean

The following snippet demonstrates how you could attempt to fill up the memory (although personally, I didn't manage to make it work due to existing memory limitations). Reference taken from @Jaroslav Tulach's answer. You may need to adjust it further according to your requirements.

function gc(max) {
    var arr = [];
    for (var i = 0; i < max; i++) {
      arr.push(i);
    }
    return arr.length;
}
//Attempt to prompt IE11 garbage collector to run
for (var i = 0; i < 10; i++) {                  // repeat until sufficient:
    gc(Math.pow(2, i));
}

Strategies for reliably causing IE 10&11 to crash? Simulating the phenomenon of "Internet Explorer abruptly closing and reopening the tab"

Answer №1

Similar questions

Jasmine was curious about how to declare a loop of 'its' rather than a loop of 'expects' when testing an Angular factory

Assistance needed with user relationships

In what way can I fill out my search fields using the criteria included in the URL?

Can you share tips for passing a variable from a post request to a function that accepts parameters as a string or an array of strings in Node.js?

The navigation bar refuses to budge towards the right side

Tips for creating a hover effect on an icon within a CSS grid

Retrieve JSON data within a service and provide it to a component

jQuery random generator for creating two-dimensional arrays

jQuery organizes information within tables

When attempting to open a native app using JavaScript, it fails to function properly. However, the same code successfully opens the

Tips for managing credentials and cookies across multiple websites

Problem with Ajax-appended form element not functioning -

Retrieving the date from a webpage

What is the best method for accessing OpenWeatherMap details via JSON?

Can a website be designed to mimic the style of the current operating system?

Implementing pagination links to trigger image changes on click

New post: The vue component that was released lacks CSS (NPM)

Discovering the version of the Javascript library utilized on a website - a step-by-step guide

Is it possible to achieve a high quality image with a file size less than 2.0MB?

Error: SyntaxError - Unexpected token 'if' found. Additionally, ReferenceError - berechnung is not defined