this post was submitted on 22 May 2026
6 points (87.5% liked)

Firefox

22774 readers
2 users here now

/c/firefox

A place to discuss the news and latest developments on the open-source browser Firefox.


Rules

1. Adhere to the instance rules

2. Be kind to one another

3. Communicate in a civil manner


Reporting

If you would like to bring an issue to the moderators attention, please use the "Create Report" feature on the offending comment or post and it will be reviewed as time allows.


founded 6 years ago
MODERATORS
 

As shown in the video. I only experience this on google translate but not sure what the exact steps to reproduce it are. I also noticed that sometimes google translate's tab memory usage grows so big, over 1 giga for the single tab, with continued prolonged usage (hours). Not sure if this is related though.

you are viewing a single comment's thread
view the rest of the comments
[–] thingsiplay@lemmy.ml 1 points 1 week ago (1 children)

Looks weird. I do not use Google Translate directly in a tab, so cannot say if the rapid changing of URL is normal or not. As for the memory usage, having it grow over time with long time usage sounds pretty normal. Even if this might be a bug, its a quasi common issue with browsers or applications with a browser under the hood leak memory. I assume reloading the page and browser should clear the RAM usage up... if it is a memory leak at all. (Many years ago I even got 8gb of leaked RAM usage in Firefox...)

[–] isVeryLoud@lemmy.ca 0 points 1 week ago (1 children)

The arbitrary code execution machine is leaking memory? Wow, surprising!

[–] thingsiplay@lemmy.ml 1 points 1 week ago (1 children)

Yes, happens with bad programming. Would be less of an issue with Rust, BTW...

[–] isVeryLoud@lemmy.ca 1 points 1 week ago (1 children)

such a meme

We'll see when the Rust browsers come to fruition. If it's full of unsafe sections because it has to run arbitrary code, it won't be worth much.

[–] thingsiplay@lemmy.ml 1 points 1 week ago

It's not a meme. Most code in Rust is safe code. Even safe code does not prevent memory leaks, but it makes it vastly less likely, because of the controlled memory management. For those places when unsafe code is used, the likelyhood of getting memory leaks rises obviously. But that is a controlled little space. Because its marked as unsafe code, there is a huge red flag and more eyes are on that part than usual. And in case of a memory issue, those are the places to look first, which in turn helps finding memory issues faster.

Compare this to C, where everything is unsafe, potentially millions lines of code. Versus a couple of hundreds of thousand lines of unsafe code in Rust, if any. You can declare it as meme if you like, but that doesn't change the facts.