mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 00:05:55 +03:00
[GH-ISSUE #867] Memory allocation of 5404319552844632832 bytes failed on connection #437
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#437
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 @pefoo on GitHub (Oct 20, 2021).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/867
Originally assigned to: @roderickvd on GitHub.
Hi,
as soon as i connect to my running librespot instance, I get the following output
Using a self build version of the v0.3.0 tag
Device that runs librespot:
I am happy to answer questions or provide logs, if you point me to them ;)
@roderickvd commented on GitHub (Oct 21, 2021):
Hey, thanks for the report. That's strange. The lowest-spec device that we target is a Raspberry Pi Zero with 512 MB RAM, and I know that worked fine for
0.2.0. Also it's requesting 5404319552 GB which makes no sense at all.Couple of questions:
--release?--releaseand provide a full stack trace with--verbose?0.2.0?@pefoo commented on GitHub (Oct 21, 2021):
Before reading the answers: I managed to solve the issue. It was (of course) my fault. More about this at the end of my post. Adding the answers for the sake of completion and later reference. (spoiler: alsa is no longer included in the default feature set, I use alsa)
--release?Yes it was
--releaseand provide a full stack trace with--verbose?Sure.
0.2.0?I did. Some days after the tag was created. Same result. Since it was that new I decided to wait. I can try again if you really want me to.
Problem solution
Reading this output made me wonder why the Rodio sink was used. Reading the latest docs clearly state, that I have to compile it with
--features alsa-backendand run with--backend alsa. Doing so solved my problem.I apologize for the false report. Should have checked the docs between versions.
Keep up the great work and thank you.
@roderickvd commented on GitHub (Oct 21, 2021):
Great that it's working for you. If I understand correctly however, it fails when using Rodio? It shouldn't, but I can't reproduce it on my RPi 3B+.
@pefoo commented on GitHub (Oct 21, 2021):
Yes that is right. It fails when it is using rodio and is compiled without the alsa feature.
If you are interested, my install / build setup is as follows (taken from my wiki, thats why in the 'execute this to get your setup done' notation) :
@roderickvd commented on GitHub (Oct 21, 2021):
Looks like an issue in
cpaland related to https://github.com/RustAudio/cpal/issues/591.@AndreKR commented on GitHub (Mar 27, 2022):
I came here because I was running into the same issue on a Pi 4.
I don't understand the issue though... Rodio is the default but it is deprecated and we're supposed to compile and run with the ALSA backend now or what? Where does it say that?
@roderickvd commented on GitHub (Apr 7, 2022):
No one said Rodio is deprecated.
Rodio is the default backend because in 99% of the cases it provides an out-of-the-box experience. Where it doesn't and/or you want the best possible performance, Alsa is the most bare metal backend on Linux that we support.
@AndreKR commented on GitHub (Apr 7, 2022):
I didn't see those docs that say I have to compile and run it with ALSA, but in fact I got the same error and in fact compiling and running it with ALSA solved it for me as well.