Project

General

Profile

Opening multiple tabs hangs in Firefox with NS_BINDING_ABORTED

Added by Harm ​ over 2 years ago

Hello,

While doing login tests with our application, we noticed Firefox would sometimes fail to (properly) load the page.
I can reproduce this with around 30 tabs open, although another user has witnessed this with as low as 10 tabs.

When new tabs stop loading, I'm getting NS_BINDING_ABORTED:

In our application, the page is empty.

I've attached a very minimal testcase which also throws the NS_BINDING_ABORTED code if I press F5 a few times.
However, the GIF does load in this case.

The testcase, though the image is loaded.

That was with add-ons disabled.

When Googling for NS_BINDING_ABORTED, I've found this Stack Overflow thread saying that I need an Expires header, so that Firefox would use the cache instead.
I'm not sure if that applies here, because I haven't seen the mentioned 304 status code.
However, I see that a few HTTP requests have Expires: 0, which is invalid according to MDN.

This email from a Mozilla engineer mentions that redirects could be cancelled with NS_BINDING_ABORTED.
Maybe this gets thrown while connecting to the WebSocket?

Can anyone reproduce this?
Does anyone have a better grasp of what's going on?

This was tested with:

  • Wt v4.6.2.
  • WebSockets enabled in wt_config.xml.
  • Firefox v97.0.1 on both Arch Linux and Windows 10.

Kind regards,
Harm.


Replies (2)

RE: Opening multiple tabs hangs in Firefox with NS_BINDING_ABORTED - Added by Harm ​ over 2 years ago

I also see the NS_BINDING_ABORTED when I refresh the Widget Gallery around 10 times.

But the page seems to load correctly.

RE: Opening multiple tabs hangs in Firefox with NS_BINDING_ABORTED - Added by Roel Standaert over 2 years ago

That just indicates that a certain request was aborted, and it may indeed occur when you're refreshing a Wt application. It's not actually an error.

There is likely some other, still unknown, cause.

    (1-2/2)