This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Pages won't load if another tab is waiting for a slow script which is on the same website

  • 1 reply
  • 5 have this problem
  • 1 view
  • Last reply by juanps90

juanps90
juanps90
more options

If there is a tab that is waiting for slow script other tabs on the same website will be affected, even though they should not.

Test case:

1. Open a tab and run a slow script ( example: http://localhost/slow_script.php ) 2. Open another tab and run a normal script ( example: http://localhost/normal_script.php )

What should happen:

The normal script will load, the slow one will be waiting for the server to finish.

What happens:

The normal script wont start loading until the slow one finishes.

Is there any way to work around this issue?

Thanks !

If there is a tab that is waiting for slow script other tabs on the same website will be affected, even though they should not. Test case: 1. Open a tab and run a slow script ( example: http://localhost/slow_script.php ) 2. Open another tab and run a normal script ( example: http://localhost/normal_script.php ) What should happen: The normal script will load, the slow one will be waiting for the server to finish. What happens: The normal script wont start loading until the slow one finishes. Is there any way to work around this issue? Thanks !

All Replies (1)

juanps90
juanps90 Question owner
more options

I have to add that the delay is not caused by the server itself. Running two web browsers or using multiple computers does the trick.

Using a simple sleep function to make the script take longer seems enough to reproduce this bug. There is no need to consume actual resources on the web server.