After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 693111 - [meta] Make PyGI marshaling leak free
[meta] Make PyGI marshaling leak free
Status: RESOLVED OBSOLETE
Product: pygobject
Classification: Bindings
Component: introspection
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Nobody's working on this now (help wanted and appreciated)
Python bindings maintainers
Depends on: 92955 510511 546802 638267 640868 657442 661359 675726 676498 685598 687522 692044 693402 694860 694862 695128 695129 695130 703960 709879 709880 726206 735013 735018 736502 736514 736517
Blocks:
 
 
Reported: 2013-02-03 21:38 UTC by Simon Feltman
Modified: 2018-01-10 20:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Simon Feltman 2013-02-03 21:38:04 UTC 
Tracking ticket to bundle up all the different tickets for fixing reference leaks and invalid GObjects being returned in some cases.

Some ideas and analysis were written up in a wiki:
https://live.gnome.org/PyGObject/Analysis/ObjectReferenceCountingForVFuncsAndClosures
Comment 1 Simon Feltman 2013-10-11 05:57:09 UTC 
Updating title a bit to reflect a general tracking of any marshaling leakage, not just relating to GObjects.
Comment 2 GNOME Infrastructure Team 2018-01-10 20:22:12 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/pygobject/issues/43.