this post was submitted on 04 Jul 2023
63 points (98.5% liked)

Firefox

1058 readers
17 users here now

The latest news and developments on Firefox and Mozilla, a global non-profit that strives to promote openness, innovation and opportunity on the web.

You can subscribe to this community from any Kbin or Lemmy instance:

Related

Rules

While we are not an official Mozilla community, we have adopted the Mozilla Community Participation Guidelines as far as it can be applied to a bin.

Rules

  1. Always be civil and respectful
    Don't be toxic, hostile, or a troll, especially towards Mozilla employees. This includes gratuitous use of profanity.

  2. Don't be a bigot
    No form of bigotry will be tolerated.

  3. Don't post security compromising suggestions
    If you do, include an obvious and clear warning.

  4. Don't post conspiracy theories
    Especially ones about nefarious intentions or funding. If you're concerned: Ask. Please don’t fuel conspiracy thinking here. Don’t try to spread FUD, especially against reliable privacy-enhancing software. Extraordinary claims require extraordinary evidence. Show credible sources.

  5. Don't accuse others of shilling
    Send honest concerns to the moderators and/or admins, and we will investigate.

  6. Do not remove your help posts after they receive replies
    Half the point of asking questions in a public sub is so that everyone can benefit from the answers—which is impossible if you go deleting everything behind yourself once you've gotten yours.

founded 1 year ago
MODERATORS
63
Firefox 115 released (www.mozilla.org)
submitted 1 year ago* (last edited 1 year ago) by hal_5700X to c/[email protected]
you are viewing a single comment's thread
view the rest of the comments
[–] A1Rayne 1 points 1 year ago* (last edited 1 year ago) (2 children)

i have a feeling there is something horribly wrong with 115.

firefox has been lagging and using too much ram. 114 was the best patch in history but now its back to the same old struggling firefox. or worse.

[–] [email protected] 2 points 1 year ago (1 children)

If you want to find the bug, you can run a mozregression to find what broke it (using 114 as your last known good release and 115 as your bad release).

Please reach out if you need help with this.

You can use your profile to test this pretty easily.

[–] A1Rayne 1 points 1 year ago* (last edited 1 year ago)

thanks ill just use vivaldi for the time being. this new version is using 10k + ram with 3 tabs open. unusable.

pitty though firefox was working so well since 112 and great since 114. this patch butchered the performance.