[Bug 2012978] Re: Memory leak
❯ apt-cache policy gjs
gjs:
Installato: 1.72.4-0ubuntu0.22.04.4
Candidato: 1.72.4-0ubuntu0.22.04.4
Tabella versione:
*** 1.72.4-0ubuntu0.22.04.4 400
400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
1.72.4-0ubuntu0.22.04.3~really.is.1.72.2.0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
1.72.0-1 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
❯ env G_SLICE=always-malloc valgrind --leak-check=full \
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
gjs -c "const GLib=imports.gi['GLib'];function leak(){const
l=GLib.Variant['new']('i',1)};leak();imports.system.gc();"
==1944776== Memcheck, a memory error detector
==1944776== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==1944776== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info
==1944776== Command: gjs -c const\ GLib=imports.gi['GLib'];function\
leak(){const\ l=GLib.Variant['new']('i',1)};leak();imports.system.gc();
==1944776==
==1944776== Warning: set address range perms: large range [0x1b8f456c7000,
0x1b8fc52c7000) (noaccess)
==1944776== Warning: set address range perms: large range [0x1b8f456c7000,
0x1b8fc52c7000) (noaccess)
==1944776==
==1944776== HEAP SUMMARY:
==1944776== in use at exit: 193,453 bytes in 2,451 blocks
==1944776== total heap usage: 20,023 allocs, 17,572 frees, 9,271,628 bytes
allocated
==1944776==
==1944776== 352 bytes in 1 blocks are possibly lost in loss record 1,970 of
2,013
==1944776==at 0x484DA83: calloc (vg_replace_malloc.c:1328)
==1944776==by 0x40147D9: calloc (rtld-malloc.h:44)
==1944776==by 0x40147D9: allocate_dtv (dl-tls.c:375)
==1944776==by 0x40147D9: _dl_allocate_tls (dl-tls.c:634)
==1944776==by 0x501F7B4: allocate_stack (allocatestack.c:430)
==1944776==by 0x501F7B4: pthread_create@@GLIBC_2.34 (pthread_create.c:647)
==1944776==by 0x5A4E794: mozilla::TimeStamp::ComputeProcessUptime() (in
/usr/lib/x86_64-linux-gnu/libmozjs-91.so.91.10.0)
==1944776==by 0x5A4E856: mozilla::TimeStamp::ProcessCreation(bool*) (in
/usr/lib/x86_64-linux-gnu/libmozjs-91.so.91.10.0)
==1944776==by 0x545CA7F: JS::detail::InitWithFailureDiagnostic(bool) (in
/usr/lib/x86_64-linux-gnu/libmozjs-91.so.91.10.0)
==1944776==by 0x48B72C3: ??? (in /usr/lib/x86_64-linux-gnu/libgjs.so.0.0.0)
==1944776==by 0x400647D: call_init.part.0 (dl-init.c:70)
==1944776==by 0x4006567: call_init (dl-init.c:33)
==1944776==by 0x4006567: _dl_init (dl-init.c:117)
==1944776==by 0x40202C9: ??? (in
/usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2)
==1944776==by 0x2: ???
==1944776==by 0x1FFEFFF84A: ???
==1944776==
==1944776== LEAK SUMMARY:
==1944776==definitely lost: 0 bytes in 0 blocks
==1944776==indirectly lost: 0 bytes in 0 blocks
==1944776== possibly lost: 352 bytes in 1 blocks
==1944776==still reachable: 77,592 bytes in 971 blocks
==1944776== suppressed: 97,829 bytes in 1,292 blocks
==1944776== Reachable blocks (those to which a pointer was found) are not shown.
==1944776== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==1944776==
==1944776== For lists of detected and suppressed errors, rerun with: -s
==1944776== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 1 from 1)
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/2012978
Title:
Memory leak
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012978] Re: Memory leak
Hello Vladimir, or anyone else affected, Accepted gjs into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gjs/1.72.4-0ubuntu0.22.04.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gjs (Ubuntu Jammy) Status: Fix Released => Fix Committed ** Tags removed: verification-done verification-done-jammy ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012978] Re: Memory leak
This bug was fixed in the package gjs - 1.72.4-0ubuntu0.22.04.3~really.is.1.72.2.0ubuntu2 --- gjs (1.72.4-0ubuntu0.22.04.3~really.is.1.72.2.0ubuntu2) jammy; urgency=medium * Revert sources to latest valid version in jammy so that people who might have had updated to the potentially unstable proposed versions are reverted to the last safe version we know (LP: #2066315): - debian/patches: Revert tree to 1.72.2 - debian/patches: Restore ubuntu patches of 1.72.2-0ubuntu2 -- Marco Trevisan (Treviño) Wed, 22 May 2024 00:39:16 +0200 ** Changed in: gjs (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012978] Re: Memory leak
** Changed in: gjs (Ubuntu Jammy) Status: Fix Released => Triaged ** Changed in: gjs (Ubuntu Jammy) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012978] Re: Memory leak
Thank you for the explanation, now I understand. People who freshly install Ubuntu 22.04 will get the updated package (and might get crashes). Existing Ubuntu users are protected from the crashes by the phasing system. And this bug is actually "fix released", because the memory leaks were fixed and the patched package is now in the Ubuntu repository. (While the crashes are a new issue.) PS: The link showing the phased update status is very handy, thanks for that as well. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012978] Re: Memory leak
Although jammy-updates has gjs at version 1.72.4-0ubuntu0.22.04.1, you probably won't receive it because crashes have been detected and so the rollout stopped: https://ubuntu-archive-team.ubuntu.com/phased-updates.html You can still install the update files manually from: https://launchpad.net/ubuntu/+source/gjs/1.72.4-0ubuntu0.22.04.1/+build/26344571 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012978] Re: Memory leak
@vanvugt is this bug still supposed to be in Triaged and did the janitor erroneously move it back to Fix Released? The package is still held back on our machines (Jammy) and still on 1.72.2 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012978] Re: Memory leak
This bug was fixed in the package gjs - 1.72.4-0ubuntu0.22.04.1 --- gjs (1.72.4-0ubuntu0.22.04.1) jammy; urgency=medium * New upstream stable release (LP: #2023572) * debian/patches: Drop, they've been all applied upstream gjs (1.72.3-0ubuntu0.22.04.1) jammy; urgency=medium * New upstream release (LP: #2023572): * debian/patches: Refresh teardown patch, replacing it with the one landed upstream (LP: #1974293) * debian/patches: Cherry-pick upstream fixes to address various memory leaks (LP: #2012978) -- Marco Trevisan (Treviño) Thu, 15 Jun 2023 17:23:40 +0200 ** Changed in: gjs (Ubuntu Jammy) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012978] Re: Memory leak
It was reverted from the archive. Jammy is back on 1.72.2-0ubuntu2 now. > @sil2100: Hey! The package was phased to 0 instantly from 10% with a lot of error reports ** Changed in: gjs (Ubuntu Jammy) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012978] Re: Memory leak
This bug was fixed in the package gjs - 1.72.4-0ubuntu0.22.04.1 --- gjs (1.72.4-0ubuntu0.22.04.1) jammy; urgency=medium * New upstream stable release (LP: #2023572) * debian/patches: Drop, they've been all applied upstream gjs (1.72.3-0ubuntu0.22.04.1) jammy; urgency=medium * New upstream release (LP: #2023572): * debian/patches: Refresh teardown patch, replacing it with the one landed upstream (LP: #1974293) * debian/patches: Cherry-pick upstream fixes to address various memory leaks (LP: #2012978) -- Marco Trevisan (Treviño) Thu, 15 Jun 2023 17:23:40 +0200 ** Changed in: gjs (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012978] Re: Memory leak
❯ apt-cache policy gjs
gjs:
Installed: 1.72.4-0ubuntu0.22.04.1
Candidate: 1.72.4-0ubuntu0.22.04.1
Version table:
*** 1.72.4-0ubuntu0.22.04.1 400
400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
1.72.2-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
1.72.0-1 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
No variant leak (the other detected is a mozjs issue, but likely a wrong
valgrind detection):
❯ env G_SLICE=always-malloc valgrind --leak-check=full \
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
gjs -c "const GLib=imports.gi['GLib'];function leak(){const
l=GLib.Variant['new']('i',1)};leak();imports.system.gc();"
==356489== Memcheck, a memory error detector
==356489== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==356489== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info
==356489== Command: gjs -c const\ GLib=imports.gi['GLib'];function\
leak(){const\ l=GLib.Variant['new']('i',1)};leak();imports.system.gc();
==356489==
==356489== Warning: set address range perms: large range [0x2204b34b7000,
0x2205330b7000) (noaccess)
==356489== Warning: set address range perms: large range [0x2204b34b7000,
0x2205330b7000) (noaccess)
==356489==
==356489== HEAP SUMMARY:
==356489== in use at exit: 193,115 bytes in 2,445 blocks
==356489== total heap usage: 19,931 allocs, 17,486 frees, 9,251,399 bytes
allocated
==356489==
==356489== 352 bytes in 1 blocks are possibly lost in loss record 1,965 of 2,008
==356489==at 0x484DA83: calloc (in
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==356489==by 0x40147D9: calloc (rtld-malloc.h:44)
==356489==by 0x40147D9: allocate_dtv (dl-tls.c:375)
==356489==by 0x40147D9: _dl_allocate_tls (dl-tls.c:634)
==356489==by 0x5008834: allocate_stack (allocatestack.c:430)
==356489==by 0x5008834: pthread_create@@GLIBC_2.34 (pthread_create.c:647)
==356489==by 0x5A36794: mozilla::TimeStamp::ComputeProcessUptime() (in
/usr/lib/x86_64-linux-gnu/libmozjs-91.so.91.10.0)
==356489==by 0x5A36856: mozilla::TimeStamp::ProcessCreation(bool*) (in
/usr/lib/x86_64-linux-gnu/libmozjs-91.so.91.10.0)
==356489==by 0x5444A7F: JS::detail::InitWithFailureDiagnostic(bool) (in
/usr/lib/x86_64-linux-gnu/libmozjs-91.so.91.10.0)
==356489==by 0x48A2363: ??? (in /usr/lib/x86_64-linux-gnu/libgjs.so.0.0.0)
==356489==by 0x400647D: call_init.part.0 (dl-init.c:70)
==356489==by 0x4006567: call_init (dl-init.c:33)
==356489==by 0x4006567: _dl_init (dl-init.c:117)
==356489==by 0x40202E9: ??? (in
/usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2)
==356489==by 0x2: ???
==356489==by 0x1FFEFFFBBE: ???
==356489==
==356489== LEAK SUMMARY:
==356489==definitely lost: 0 bytes in 0 blocks
==356489==indirectly lost: 0 bytes in 0 blocks
==356489== possibly lost: 352 bytes in 1 blocks
==356489==still reachable: 77,254 bytes in 965 blocks
==356489== suppressed: 97,829 bytes in 1,292 blocks
==356489== Reachable blocks (those to which a pointer was found) are not shown.
==356489== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==356489==
==356489== For lists of detected and suppressed errors, rerun with: -s
==356489== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 1 from 1)
-
env GJS_DEBUG_TOPICS= valgrind --leak-check=full \
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
/usr/libexec/installed-tests/gjs/minijasmine \
/usr/libexec/installed-tests/gjs/js/testGIMarshalling.js
==357068== Warning: set address range perms: large range [0xbabd0a0c000,
0xbac5060c000) (noaccess)
==357068==
==357068== HEAP SUMMARY:
==357068== in use at exit: 231,169 bytes in 3,087 blocks
==357068== total heap usage: 155,879 allocs, 152,792 frees, 28,688,797 bytes
allocated
==357068==
==357068== 0 bytes in 1 blocks are definitely lost in loss record 1 of 2,526
==357068==at 0x4848899: malloc (in
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==357068==by 0x4005A22: malloc (rtld-malloc.h:56)
==357068==by 0x4005A22: _dl_find_object_update (dl-find_object.c:791)
==357068==by 0x400ECCF: dl_open_worker_begin (dl-open.c:735)
==357068==by 0x4EC0C27: _dl_catch_exception (dl-error-skeleton.c:208)
==357068==by 0x400DF99: dl_open_worker (dl-open.c:782)
==357068==by 0x4EC0C27: _dl_catch_exception (dl-error-skeleton.c:208)
==357068==by 0x400E34D: _dl_open (dl-open.c:883)
==357068==by 0x4DDC6BB: dlopen_doit (dlopen.c:56)
==357068==by 0x4EC0C27: _dl_catch_exception (dl-error-skeleton.c:208)
==357068==by 0x4EC0CF2: _dl_catch_error (dl-error-skeleton.c:227)
==357068==by 0x4DDC1AD: _dlerror_run (dlerror.c:138)
==357068==by 0x4DDC747: dlopen_implementation (dlopen.c:71)
==357068==by 0x4DDC747: dlopen@@GLIBC_2.34 (dlope
[Bug 2012978] Re: Memory leak
Hello Vladimir, or anyone else affected, Accepted gjs into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gjs/1.72.4-0ubuntu0.22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gjs (Ubuntu Jammy) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012978] Re: Memory leak
** Description changed:
[ Impact ]
High Memory Usage 3.1gb in 2h after reboot
[ Test case ]
Run:
- env G_SLICE=always-malloc valgrind --leak-check=full \
- --suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
- gjs -c "const GLib=imports.gi['GLib'];function leak(){const
l=GLib.Variant['new']('i',1)};leak();imports.system.gc();"
+ env G_SLICE=always-malloc valgrind --leak-check=full \
+ --suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
+ gjs -c "const GLib=imports.gi['GLib'];function leak(){const
l=GLib.Variant['new']('i',1)};leak();imports.system.gc();"
No leak should be detected
+
+ Running more installed tests under valgrind should output no leaks
+ (unless those caused by gobject-introspection):
+
+ sudo apt install gjs-tests
+ env GJS_DEBUG_TOPICS= valgrind --leak-check=full \
+ --suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
+ /usr/libexec/installed-tests/gjs/minijasmine \
+ /usr/libexec/installed-tests/gjs/js/testGIMarshalling.js
+
+ There may be only two leaks caused by
+ gi_marshalling_tests_garray_boxed_struct_full_return and a gbytes one
+ after a ObjectInstance::prop_setter_impl call (these are leaks in the
+ test library that are expected with gobject-introspection 42, but fixed
+ in later versions).
+
+ env GJS_DEBUG_TOPICS= valgrind --leak-check=full \
+ --suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
+ /usr/libexec/installed-tests/gjs/minijasmine \
+ /usr/libexec/installed-tests/gjs/js/testRegress.js
+
+ No leak expected
[ Regression potential ]
Gjs applications (including gnome Shell) using GVariant may misbehave
+ ---
ProblemType: BugDistroRelease: Ubuntu 22.04
Package: gnome-shell 42.5-0ubuntu1
Uname: Linux 6.2.8-060208-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 27 22:46:07 2023
DisplayManager: gdm3
InstallationDate: Installed on 2022-03-25 (366 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
RelatedPackageVersions: mutter-common 42.5-0ubuntu1SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-09-03 (205 days ago)
** Changed in: gjs (Ubuntu Kinetic)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/2012978
Title:
Memory leak
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012978] Re: Memory leak
** Changed in: gjs (Ubuntu Jammy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012978] Re: Memory leak
Currently we're getting
❯ env G_SLICE=always-malloc valgrind --leak-check=full
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp gjs -c "const
GLib=imports.gi['GLib'];function leak(){const
l=GLib.Variant['new']('i',1)};leak();imports.system.gc();"
==131398== Memcheck, a memory error detector
==131398== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==131398== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info
==131398== Command: gjs -c const\ GLib=imports.gi['GLib'];function\
leak(){const\ l=GLib.Variant['new']('i',1)};leak();imports.system.gc();
==131398==
==131398== Warning: set address range perms: large range [0x1663bc3af000,
0x16643bfaf000) (noaccess)
==131398== Warning: set address range perms: large range [0x1663bc3af000,
0x16643bfaf000) (noaccess)
==131398==
==131398== HEAP SUMMARY:
==131398== in use at exit: 191,779 bytes in 2,483 blocks
==131398== total heap usage: 18,733 allocs, 16,250 frees, 8,376,620 bytes
allocated
==131398==
==131398== 108 (64 direct, 44 indirect) bytes in 1 blocks are definitely lost
in loss record 1,885 of 2,041
==131398==at 0x4844899: malloc (in
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==131398==by 0x4A22948: g_malloc (gmem.c:130)
==131398==by 0x4A6598F: UnknownInlinedFun (gvariant-core.c:565)
==131398==by 0x4A6598F: g_variant_new_from_bytes (gvariant-core.c:608)
==131398==by 0x4A65EF3: UnknownInlinedFun (gvariant.c:327)
==131398==by 0x4A65EF3: g_variant_new_int32 (gvariant.c:491)
==131398==by 0x51B8E2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
==131398==by 0x51B5492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
==131398==by 0x48C8198: ??? (in /usr/lib/x86_64-linux-gnu/libgjs.so.0.0.0)
==131398==by 0x48C8A06: ??? (in /usr/lib/x86_64-linux-gnu/libgjs.so.0.0.0)
==131398==by 0x532FC81: js::InternalCallOrConstruct(JSContext*,
JS::CallArgs const&, js::MaybeConstruct, js::CallReason) (Interpreter.cpp:420)
==131398==by 0x533A46B: UnknownInlinedFun (Interpreter.cpp:574)
==131398==by 0x533A46B: UnknownInlinedFun (Interpreter.cpp:578)
==131398==by 0x533A46B: Interpret(JSContext*, js::RunState&) [clone
.lto_priv.0] (Interpreter.cpp:3314)
==131398==by 0x532F692: js::RunScript(JSContext*, js::RunState&)
(Interpreter.cpp:389)
==131398==by 0x532FA8E: js::InternalCallOrConstruct(JSContext*,
JS::CallArgs const&, js::MaybeConstruct, js::CallReason) (Interpreter.cpp:539)
==131398==
==131398== 352 bytes in 1 blocks are possibly lost in loss record 1,999 of 2,041
==131398==at 0x4849A83: calloc (in
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==131398==by 0x4012949: calloc (rtld-malloc.h:44)
==131398==by 0x4012949: allocate_dtv (dl-tls.c:375)
==131398==by 0x4012949: _dl_allocate_tls (dl-tls.c:634)
==131398==by 0x5019F99: allocate_stack (allocatestack.c:423)
==131398==by 0x5019F99: pthread_create@@GLIBC_2.34 (pthread_create.c:650)
==131398==by 0x5A97B54: mozilla::TimeStamp::ComputeProcessUptime()
(TimeStamp_posix.cpp:275)
==131398==by 0x5A97BE7: mozilla::TimeStamp::ProcessCreation()
(TimeStamp.cpp:62)
==131398==by 0x53FD5FC: JS::detail::InitWithFailureDiagnostic(bool)
(Initialization.cpp:145)
==131398==by 0x48A3E25: ??? (in /usr/lib/x86_64-linux-gnu/libgjs.so.0.0.0)
==131398==by 0x4004FBD: call_init.part.0 (dl-init.c:70)
==131398==by 0x40050A7: call_init (dl-init.c:33)
==131398==by 0x40050A7: _dl_init (dl-init.c:117)
==131398==by 0x401D8AF: ??? (in
/usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2)
==131398==by 0x2: ???
==131398==by 0x1FFEFFF606: ???
==131398==
==131398== LEAK SUMMARY:
==131398==definitely lost: 64 bytes in 1 blocks
==131398==indirectly lost: 44 bytes in 2 blocks
==131398== possibly lost: 352 bytes in 1 blocks
==131398==still reachable: 75,986 bytes in 985 blocks
==131398== suppressed: 97,525 bytes in 1,306 blocks
==131398== Reachable blocks (those to which a pointer was found) are not shown.
==131398== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==131398==
==131398== For lists of detected and suppressed errors, rerun with: -s
==131398== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 2 from 2
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/2012978
Title:
Memory leak
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012978] Re: Memory leak
** Also affects: gjs (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: gjs (Ubuntu Kinetic) Status: New => Triaged ** Changed in: gjs (Ubuntu Kinetic) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012978] Re: Memory leak
** Description changed:
+ [ Impact ]
+
High Memory Usage 3.1gb in 2h after reboot
- ProblemType: Bug
- DistroRelease: Ubuntu 22.04
+ [ Test case ]
+
+ Run:
+ env G_SLICE=always-malloc valgrind --leak-check=full \
+ --suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
+ gjs -c "const GLib=imports.gi['GLib'];function leak(){const
l=GLib.Variant['new']('i',1)};leak();imports.system.gc();"
+
+ No leak should be detected
+
+ [ Regression potential ]
+
+ Gjs applications (including gnome Shell) using GVariant may misbehave
+
+
+ ProblemType: BugDistroRelease: Ubuntu 22.04
Package: gnome-shell 42.5-0ubuntu1
Uname: Linux 6.2.8-060208-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 27 22:46:07 2023
DisplayManager: gdm3
InstallationDate: Installed on 2022-03-25 (366 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
- RelatedPackageVersions: mutter-common 42.5-0ubuntu1
- SourcePackage: gnome-shell
+ RelatedPackageVersions: mutter-common 42.5-0ubuntu1SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-09-03 (205 days ago)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/2012978
Title:
Memory leak
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012978] Re: Memory leak
Gjs was definitely leak from 22.04 any GVariant, so that will be backported to jammy too but it requires some more testing in interim release first. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012978] Re: Memory leak
I'm not sure this generic leak bug should have been declared fixed in the absence of additional information. Maybe Marco knew what it was from the repeating log message: ubuntu-appindicat...@ubuntu.com[3923]: unable to update icon for multiload If you experience any other problems (including leaks) then please open new bugs of your own. Don't assume existing bugs that sound similar to your experience are the same issue. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012978] Re: Memory leak
What about 22.04 LTS? This bug fixed for 23.04 but not for 22.04. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012978] Re: Memory leak
This bug was fixed in the package gjs - 1.76.0-3 --- gjs (1.76.0-3) experimental; urgency=medium * debian/patches: Drop patch causing GNOME Characters not to show emojis (LP: #2015948) gjs (1.76.0-2) experimental; urgency=medium [ Daniel van Vugt ] * Add context-Clear-all-vectors-of-JS-Heap-on-dispose.patch (LP: #1974293) [ Marco Trevisan (Treviño) ] * debian/patches: Do not leak GVariants and other handled objects (LP: #1991709, #2012978) -- Marco Trevisan (Treviño) Wed, 12 Apr 2023 05:40:15 +0200 ** Changed in: gjs (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012978] Re: Memory leak
** Changed in: gjs (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012978] Re: Memory leak
** Package changed: gnome-shell (Ubuntu) => gjs (Ubuntu) ** Changed in: gjs (Ubuntu) Status: Incomplete => In Progress ** Changed in: gjs (Ubuntu) Importance: Undecided => High ** Changed in: gjs (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Also affects: gjs (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gjs (Ubuntu Jammy) Importance: Undecided => High ** Changed in: gjs (Ubuntu Jammy) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012978] Re: Memory leak
Also it looks like you are experiencing bug 1988791. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012978] Re: Memory leak
Thanks for the bug report. When the problem is happening next, please run: ps auxw | grep gnome-shell > psgs.txt and attach the resulting text file here. ** Tags added: gnome-shell-leak ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012978] Re: Memory leak
the cmd: gnome-extensions list --enabled shows: ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com d...@rastersoft.com disabling extensions does not make effects -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
