this post was submitted on 25 Jul 2026
3 points (100.0% liked)
techsupport
3211 readers
1 users here now
The Lemmy community will help you with your tech problems and questions about anything here. Do not be shy, we will try to help you.
If something works or if you find a solution to your problem let us know it will be greatly apreciated.
Rules: instance rules + stay on topic
Partnered communities:
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Fsync will write data that your userspace program has already handed off to the OS. This probably won't be your problem; your OS's kernel should already write out that data if it's under memory pressure. Assuming that this is Linux, you can twiddle Linux's kernel settings to make it write out more frequently. The
synccommand will also write out existing data that hasn't been written to the kernel, and you could do something like$ while true; do sleep 1; sync; done.But you probably have an issue inside the application, not in handling data that needs to be fsynced.
I'd also add that I'd be a little surprised if this happens with Firefox's native downloading. Maybe someone could have some sort of custom download Javascript something-or-other that stages stuff in memory on a website, though I don't think that even a poorly-written Javascript should be able to produce a tab crashing.
Those are some amazing ideas and insights! I'll try that intermittent
syncjust for the fun of it, but I'll also check if I can loosen up Librewolf's anti fingerprinting and whatnot. Probably messing with lots of common functions, JS included.