mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 00:05:55 +03:00
[GH-ISSUE #1648] requir too much memory and failed #750
Labels
No labels
A-Alsa
SpotifyAPI
Tokio 1.0
audio
bug
can't reproduce
compilation
dependencies
duplicate
enhancement
good first issue
help wanted
high priority
imported
imported
invalid
new api
pull-request
question
reverse engineering
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/librespot#750
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @andygaof on GitHub (Nov 19, 2025).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/1648
Look for similar bugs
Please check if there's already an issue for your problem, and you're running at least the latest release.
If you've only a "me too" comment to make, consider if a 👍 reaction
will suffice.
Description
when librespot setup connection, it requires too much memory, more than 1GB, and failed, then exit.
tried three startup parameters, same
Version
What version(s) of librespot does this problem exist in?
0.8.0
How to reproduce
Steps to reproduce the behavior in librespot e.g.
librespotwithlibrespot --backend alsa --format S32 --bitrate 320 --name SpotifyArm --verbose or librespot --backend alsa --format S32 --bitrate 320 --name SpotifyArm --initial-volume 100 --verboseorlibrespot --backend alsa --format S32 --bitrate 320 --name SpotifyArm --initial-volume 100 --tmp /tmp --cache /tmp --system-cache /tmp --cache-size-limit 20M --verboseLog
librespot --backend alsa --format S32 --bitrate 320 --name SpotifyArm --initial-volume 100 --tmp /tmp --cache /tmp --system-cache /tmp --cache-size-limit 20M --verboselibrespot --backend alsa --format S32 --bitrate 320 --name SpotifyArm --initial-volume 100 --verboselibrespot --backend alsa --format S32 --bitrate 320 --name SpotifyArm --verboseHost (what you are running
librespoton):Additional context
Add any other context about the problem here. If your issue is related to sound playback, at a minimum specify the type and make of your output device.
@kingosticks commented on GitHub (Nov 19, 2025):
The first step would always be to run the debug profile. And then also run that under gdb. You're going to have to do that.
You could also quickly try a different bitrate to see if that allocation size changes and then that's a big hint.
@herrernst commented on GitHub (Dec 28, 2025):
Why do you need/set
--format S32?with-vorbisandwith-tremorfeatures #1057