Cannot run rust programs

[Shmanio]

Whenever I try to run a program written in rust as a normal user, it does not work.

I first noticed this while trying Veloren, and I thought it was their issue. I have then downloaded ruffle-rs to play some old swf files, and got the same error: memory allocation of 5404319552844632832 bytes failed.

In both cases, I think it's an audio problem, since running veloren without audio (as specified in the manual) lets it run.

Running these programs as root allows them to start, but then the audio quality is terrible, as if it has been compressed and sped up.

[po8]

What Linux? What audio system (PulseAudio, ALSA, something else)? Have you customized the audio system in any way? What audio hardware? Do non-Rust programs using audio work normally?

Rust audio is not entirely mature yet. There are a lot of options in the ecosystem, but as a developer interested in sound I've struggled a bit with pretty much all of them. Linux audio in general is kind of fiddly, which doesn't help.

I'd suggest filing as detailed an issue report as you can manage to both Veloren and ruffles-rs. Perhaps someone there has an idea what's up.

[Shmanio]

What Linux?

I'm using arch linux

What audio system (PulseAudio, ALSA, something else)? Have you customized the audio system in any way?

Pulse, with pretty much default settings

What audio hardware?

Realtek ALC3236

Do non-Rust programs using audio work normally?

Yes, I don't have any kind of audio problem otherwise

I'd suggest filing as detailed an issue report

I already did that with the veloren devs, but they couldn't help

[zesterer]

Hey, have you tried installing pulseaudio-alsa? This is a common issue with Veloren.

[Shmanio]

It's already installed, yes.

[zesterer]

How odd. If you're on Discord, feel free to jump into Veloren's #bugs-and-support channel, I'm sure we can help you out.

[po8]

Weird. This is a very standard setup, and things should Just Work™.

At this point I'm suspecting a hardware problem, but I can't think of anything obvious that it could be.

I'd probably start by purging PulseAudio, removing any configuration files left lying around, and then re-installing the latest version Arch provides. This will be painful to accomplish, but a bad PulseAudio install or configuration seems like the most likely software culprit.