[Bug]: v2.8.0 "MemoryStore is not designed for a production environment, as it will leak memory, and will not scale past a single process" #1779

Closed
opened 2026-04-24 23:58:00 +02:00 by adam · 1 comment
Owner

Originally created by @bendmunk95 on GitHub (Feb 28, 2024).

Describe the issue

Each time I try to scan an audiobook library, the socket disconnects about 5 seconds later and the scan does not occur. In the logs, I found this:

Warning: connect.session() MemoryStore is not designed for a production environment, as it will leak memory, and will not scale past a single process.

I'm running v2.8.0 in docker, no memory or CPU limits. I had watcher turned off, scanning libraries manually. Turning watcher on or off yields no different results. The issue seems to be if I have a directory labeled with [Any Text Here] is used. I'd love to be able to use brackets for tagging certain directories, but I understand this fix may be low priority.

Steps to reproduce the issue

  1. Attempt Library Scan with a audiobook directory beginning with [Any text here]

Audiobookshelf version

v2.8.0

How are you running audiobookshelf?

Docker

Originally created by @bendmunk95 on GitHub (Feb 28, 2024). ### Describe the issue Each time I try to scan an audiobook library, the socket disconnects about 5 seconds later and the scan does not occur. In the logs, I found this: `Warning: connect.session() MemoryStore is not designed for a production environment, as it will leak memory, and will not scale past a single process.` I'm running v2.8.0 in docker, no memory or CPU limits. I had watcher turned off, scanning libraries manually. Turning watcher on or off yields no different results. The issue seems to be if I have a directory labeled with `[Any Text Here]` is used. I'd love to be able to use brackets for tagging certain directories, but I understand this fix may be low priority. ### Steps to reproduce the issue 1. Attempt Library Scan with a audiobook directory beginning with `[Any text here]` ### Audiobookshelf version v2.8.0 ### How are you running audiobookshelf? Docker
adam added the bug label 2026-04-24 23:58:00 +02:00
adam closed this issue 2026-04-24 23:58:01 +02:00
Author
Owner

@advplyr commented on GitHub (Feb 28, 2024):

That warning is already reported here https://github.com/advplyr/audiobookshelf/issues/2538 and should not have anything to do with your issue.

The directory starting with [Any Text Here] should also not be your issue since this works fine.

Please check your crash logs in /metadata/logs/crash_logs.txt

@advplyr commented on GitHub (Feb 28, 2024): That warning is already reported here https://github.com/advplyr/audiobookshelf/issues/2538 and should not have anything to do with your issue. The directory starting with `[Any Text Here]` should also not be your issue since this works fine. Please check your crash logs in `/metadata/logs/crash_logs.txt`
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#1779