• KoolKai
    link
    fedilink
    21 year ago

    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
      link
      1
      edit-2
      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.