2 ms·
>Now if they can only fix the memory leak, that chews up gigs of RAM in only an hour. I recently quit Firefox on Linux (they no longer support ALSA and require
by BeetleB 9y ago
>Now if they can only fix the memory leak, that chews up gigs of RAM in only an hour.
I recently quit Firefox on Linux (they no longer support ALSA and require PulseAudio for sound). I used to think FF was a memory hog. Moved to Vivalidi (Chrome based). Consumes more memory and I'm sure it has a memory leak. On FF I would have ~ 30-60 tabs open. On Vivaldi it's 10-20. I have to close Vivaldi every few days to reclaim the memory.
- xoroshiro 9y agoJust curious, because I was thinking of using PulseAudio just for Firefox (which is kind of annoying). What's wrong with PulseAudio? Why did they stop supporting ALSA?
- BeetleB 9y agoI tried PulseAudio some years ago and could not get everything to work. I'm sure if I really tinkered with settings/config files, I could - but everything was working with ALSA out of the box, so I didn't bother. Pulseaudio is sold as easier to manage, but for me it simply wasn't. The assumption is that people are running systemd, and Pulseaudio presumably works well with that. But I'm not on systemd. If my distribution had a simple way of running pulseaudio and have it work more or less right out of the box, I'd go for it. But it doesn't. They stopped supporting it because no developer stepped up to support it - that's all. Apparently the Pulseaudio API is straightforward for developers, whereas dealing with ALSA directly is not.