Error: Script terminated by timeout

[bernd-wechner]

Iris version

3.70.0

Operating system(s) affected

• Windows
• MacOS
• iOS
• Android
• Linux
• Other

Browser(s) affected

• Firefox
• Chrome
• Edge
• Other

What happened?

Clicked Tracks.
Like the progress bar.
Have a rather large library, and it's counting up to: 239120

It never completes though. Always at some point, about 2/3 of the way through it hangs. By watching the browser console I can see that is at the point it issues an error like:

Error: Script terminated by timeout at:
fe@http://mopidy.me:6680/iris/app.min.js?v=1746265932:2:1285628
Un<.core<@http://mopidy.me:6680/iris/app.min.js?v=1746265932:2:1403338
V/<@http://mopidy.me:6680/iris/app.min.js?v=1746265932:2:1282546
Un</<@http://mopidy.me:6680/iris/app.min.js?v=1746265932:2:1401615
zn@http://mopidy.me:6680/iris/app.min.js?v=1746265932:2:1419305
d@http://mopidy.me:6680/iris/app.min.js?v=1746265932:2:1275762
En</</</<@http://mopidy.me:6680/iris/app.min.js?v=1746265932:2:1397199
rn/</<@http://mopidy.me:6680/iris/app.min.js?v=1746265932:2:1381241
Jr/</<@http://mopidy.me:6680/iris/app.min.js?v=1746265932:2:1380918
dn/</<@http://mopidy.me:6680/iris/app.min.js?v=1746265932:2:1386955
xr</</</<@http://mopidy.me:6680/iris/app.min.js?v=1746265932:2:1344823
Kr</</</<@http://mopidy.me:6680/iris/app.min.js?v=1746265932:2:1354813
mr/</<@http://mopidy.me:6680/iris/app.min.js?v=1746265932:2:1330095
lr/</<@http://mopidy.me:6680/iris/app.min.js?v=1746265932:2:1324224
re/</</<@http://mopidy.me:6680/iris/app.min.js?v=1746265932:2:1284185
dispatch@http://mopidy.me:6680/iris/app.min.js?v=1746265932:2:1276936
n/<@http://mopidy.me:6680/iris/app.min.js?v=1746265932:2:1379898
  
app.min.js:2:1285628

It's at a a different track count each time. Playlists, Artists, Albums and Browse all work fine. Only Tracks times out.

If this is a timer on the whole load, no wonder on a large library, and perhaps the timeout needs to increase, or is there a need for one? It takes as long as it takes and there's an incrementing progress counter so all is good.

If it's a timeout on a specific request to mopidy, I'm not seeing anything on the mopidy console and and Android clients seem to still be talking to it, as does Argos, so it'd be good to have some more details to go on. Eitehr way it appears not to be related to a specific track as it's changing between attempts. And much rather related to some resource or other (memory for example) that is hitting a limit.

Would be nice to diagnose and fix. Iris is, otherwise, quite pleasing.

[bernd-wechner]

The "Other" under Browsers was Pale Moon. I tried debugging but it doesn't allow drill down into websocket traffic. So I tried in Firefox, which does. Interesting observations:

1. Firefox actually runs to completion and displays all 239120.
2. There is no traffic on the websocket as the progress counter goes up
3. Pausing in the debugger does not stop the progress counter going up (some wicked web trickery there, last I checked the JS engine was single threaded, but did support event loop call backs and I might have to get a little smarter to spot those and watch them (have done in past from memory, been a while).

I will try other browsers out of interest. But it looks like a browser specific observation now. Still one that puzzles me. Namely what the reported timeout refers to.

[bernd-wechner]

That said, given how awesome this web client is, I can't help but wonder why it doesn't implement paging and page by page loading of the information it needs, with page size in items configurable. That's pretty ordinary for any data queries today that might return more than a few hundred results. Or?

[jaedb]

Awesome digging into the issue! To make your life easier, I'll point you to Test Mode which will run the non-minified code and hopefully provide more helpful context to trace the underlying cause of the issue.

It'd also be interesting to observe the memory and CPU usage of your machine; is it struggling to handle the interface when your quarter-of-a-million tracks are trying to be loaded? Yes, Iris does only render what is within the viewport, however it still needs to process them.