Marco Trevisan :ubuntu:
@trevi.me
Marco «Treviño» Trevisan: an Opensource Developer, Free Software advocate, @ubuntu :ubuntu: member, @debian :debian: maintainer, Canonical and @gnome :gnome: Software […]
🌉 bridged from ⁂ https://fosstodon.org/@3v1n0, follow @ap.brid.gy to interact
🌉 bridged from ⁂ https://fosstodon.org/@3v1n0, follow @ap.brid.gy to interact
@SnoopJ no sadly the only thing would be adding some debug code and see what's happening... Using `G_MESSAGES_DEBUG=AppIndicator-and-KStatusNotifierItem-Support` may help to get more debug data, but I'm unsure if it would be helpful to understand the root cause
December 14, 2025 at 10:25 PM
@SnoopJ no sadly the only thing would be adding some debug code and see what's happening... Using `G_MESSAGES_DEBUG=AppIndicator-and-KStatusNotifierItem-Support` may help to get more debug data, but I'm unsure if it would be helpful to understand the root cause
@SnoopJ Ah ok, reason why I wasn't aware of a proper "leak", memory hog could be a thing but mostly depending on applications themselves TBH.
The fact is the extension is basically just doing what the applications asks to (which is a weak point of the protocol more than anything).
On the […]
The fact is the extension is basically just doing what the applications asks to (which is a weak point of the protocol more than anything).
On the […]
Original post on fosstodon.org
fosstodon.org
December 14, 2025 at 10:16 PM
@SnoopJ Ah ok, reason why I wasn't aware of a proper "leak", memory hog could be a thing but mostly depending on applications themselves TBH.
The fact is the extension is basically just doing what the applications asks to (which is a weak point of the protocol more than anything).
On the […]
The fact is the extension is basically just doing what the applications asks to (which is a weak point of the protocol more than anything).
On the […]
@pojntfx congrats, this is getting nice!
Wondering how much we could rely on go GC though rather than manual memory management
I suspect also https://gitlab.gnome.org/GNOME/glib/-/merge_requests/4010 has helped for some low level stuff
Wondering how much we could rely on go GC though rather than manual memory management
I suspect also https://gitlab.gnome.org/GNOME/glib/-/merge_requests/4010 has helped for some low level stuff
gmain: Use alternate signal stack if the application provides one (!4010) · Merge requests · GNOME / GLib · GitLab
Some applications, toolkits or languages may define an alternative stack to use for traces. This is for example the case of go. So, in case an...
gitlab.gnome.org
December 10, 2025 at 12:23 PM
@pojntfx congrats, this is getting nice!
Wondering how much we could rely on go GC though rather than manual memory management
I suspect also https://gitlab.gnome.org/GNOME/glib/-/merge_requests/4010 has helped for some low level stuff
Wondering how much we could rely on go GC though rather than manual memory management
I suspect also https://gitlab.gnome.org/GNOME/glib/-/merge_requests/4010 has helped for some low level stuff