[Bug]: Podcast episode rows disappear while listening for a long period of time.

[tymscar]

What happened?

After listening to an hour or so of podcasts, some of the episode tiles disappear. I have managed to take a screenshot:

What did you expect to happen?

I expect to always see all the episodes in the list, depending on the filters applied.

Steps to reproduce the issue

1. Open audiobookshelf
2. Go to the podcasts tab
3. Start an episode that takes a long time (1+ hours), or just listen to multiple shorter episodes
4. Scroll around and notice how some of the tiles are blank (sometimes 20+ tiles, sometimes all, sometimes one)

Audiobookshelf version

V2.8.0

How are you running audiobookshelf?

Docker

What OS is your Audiobookshelf server hosted from?

Linux

If the issue is being seen in the UI, what browsers are you seeing the problem on?

Other (list in "Additional Notes" box)

Logs

I have noticed it on Chrome and Firefox on Linux, on Arc (Chromium), Firefox, and Safari on macOS, and on Firefox on Windows.

Additional Notes

This issue has been present in every version I've tried for the past a year and a half, so it's not a bug with a recent commit. I have also noticed it on every desktop OS, and browser. The bug is not present on the iOS application, so I suspect its a CSS issue, but I can't confirm.
The console is clean of any errors when the bug happens, here is a screenshot:

[nichwall]

Looks like the websocket is closing and the lazy loading of new podcast episodes takes a bit to connect and start loading new items.

Related behavior #2950 (comment)

[tymscar]

The websocket might've closed there just out of inactivity. Im not sure if that's the issue, as there aren't that many audiobooks in this library. Maybe 10?

[advplyr]

Are new episodes being downloaded? Do you have automatic library scans enabled?

[tymscar]

I do have automatic library scans enabled, no new episodes where downloaded when that issue happened. A lot of time I listen to super old podcasts that dont even launch new episodes anymore and I still find this bug.

[tymscar]

Would you suggest for anything to look for when it happens? Perhaps some test I could run? Some logs I should look for?