Announcement

Collapse
No announcement yet.

The Big GNOME Shell Memory Leak Has Been Plugged, Might Be Backported To 3.28

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • The Big GNOME Shell Memory Leak Has Been Plugged, Might Be Backported To 3.28

    Phoronix: The Big GNOME Shell Memory Leak Has Been Plugged, Might Be Backported To 3.28

    The widely talked about "GNOME Shell memory leak" causing excessive memory usage after a while with recent versions of GNOME has now been fully corrected. The changes are currently staged in Git for what will become GNOME 3.30 but might also be backported to 3.28...

    http://www.phoronix.com/scan.php?pag...emory-Leak-Fix

  • #2
    Looks good! The blog post also includes an outlook to further performance work. GNOME shell always had mediocre performance, I wonder why it took so long to address this. There are quite a few low hanging fruit.

    Comment


    • #3
      Just updated to 3.28.1 on Debian and now I have a loop login condition that can't be passed right after GJS was updated. This is the third time it's happened during a point release update within Debian since the 3.20+ days.

      Comment


      • #4
        Fixes like this should come not under 'might' be backported, but under MUST be backported. Gnome3 is not light as it is, why leave known memory leaks unpatched is beyond my understanding.

        Comment


        • #5
          Originally posted by blacknova View Post
          Fixes like this should come not under 'might' be backported, but under MUST be backported. Gnome3 is not light as it is, why leave known memory leaks unpatched is beyond my understanding.
          Because they first need to establish that they *can* backport it... there's no guarantee that a fix that works on the dev branch can be safely ported to a stable branch without bringing with it a ton of other changes that the fix is built on top of.

          Comment


          • #6
            Originally posted by Delgarde View Post

            Because they first need to establish that they *can* backport it... there's no guarantee that a fix that works on the dev branch can be safely ported to a stable branch without bringing with it a ton of other changes that the fix is built on top of.
            This is the correct answer.

            Comment


            • #7
              What people where thinking when they decided to use javascript for the DE in the first place..

              Comment


              • #8
                Originally posted by tessio View Post
                What people where thinking when they decided to use javascript for the DE in the first place..
                Yeah, cocaine is one hell of a drug..

                Comment


                • #9
                  What are people thinking when they decide to criticise developers for completely sensible choices?

                  FYI. Most of Firefox is written in JavaScript. A lot of good things are.

                  Comment


                  • #10
                    Ubuntu has already backported it: https://lists.ubuntu.com/archives/bi...il/014088.html

                    Comment

                    Working...
                    X