• 0 Posts
  • 7 Comments
Joined 6 months ago
cake
Cake day: June 7th, 2025

help-circle



  • Poor kid had no idea what was happening. Can we just take a moment to address what was actually going on in the background of this video? We had multiple people just blaring their horns (assuming car horns). To show discontent? To show solidarity? Because the lives of a family being torn apart was an inconvenience to them carrying out their day?

    Then we had a guy just repeating “Child endangerment” while standing behind a barrier recording on his phone. That child was 100% in danger when the vehicle they were traveling in was seemingly rammed from behind. In very little danger when surrounded by armed enforcers and will no doubt be in considerable danger again when thrown to the wolves of ICE(kids). If I truly felt a child was in danger I would have marched right through the mob in order to help said child. Regardless of the chances of getting shot or beaten. Crying wolf from the sidelines doesn’t help anyone at all!

    We had someone suggesting that the detainee should kneel down while being forceably restrained and carted off… At first I thought this may have been citizen advice to “stop resisting” but it appears it was the opposite and someone was suggesting a better way to resist. Seriously, WTF? Cross the barrier and kneel on front of the officers in order to make yourself a hindrance. No doubt you’d be slapped with trumped-up charges but that’s the price you pay in order to let everybody know that you don’t agree with this. Don’t encourage others and let them deal with the consequences while you pat yourself on the back and sleep soundly in your own bed at night.

    Then we had multiple people approach the vehicle while it was being driven away to get some closeup shots of the masked enforcers abducting the child, some complaining that they couldn’t get a clear shot of the child as they had covered their face…

    Is this what passes as a counter-ICE protest these days? For shame.


  • Here is a link to one of the bug reports: https://bugzilla.mozilla.org/show_bug.cgi?id=1897006

    Said report was closed down and presumed “fixed” but I still encounter this issue on the latest stable.

    When you know what to search for you’ll find numerous users reporting similar behaviour on Reddit and other social platforms going back multiple years.

    If I were more invested I would keep submitting bug reports and memory dumps in the hopes that it may once and for all get stomped. But I’ve made the leap back to chromium and can’t justify the time. I realise that this is a major issue but one that only affects a small percentage of users, likely affecting specific hardware / setups. If the developers aren’t able to reproduce it then it’ll probably remain unfixed.


  • I ditched Firefox due to a vicious memory leak which was so hard to track down (didn’t register in task manager) that I reinstalled windows before finding the culprit. As soon as I identified Firefox as the cause and then, when I knew what to search for, discovered it was a known bug existing for years I ditched the browser with prejudice.