8
URL on google translate keeps changing back and forth rapidly (imgur.com)
submitted 5 months ago by to c/firefox@lemmy.ml
5 comments fedilink hide all child comments
 

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
[–] 1 point 5 months ago (4 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...)

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] 1 point 5 months ago (3 children)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 5 months ago (2 children)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 5 months ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 5 months 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.

  • permalink
  • fedilink
  • source
  • parent