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 689267 - GVariant properties with default value cause segfault
GVariant properties with default value cause segfault
Status: RESOLVED FIXED
Product: pygobject
Classification: Bindings
Component: introspection
Git master
Other Linux
: High major
: ---
Assigned To: Martin Pitt
Python bindings maintainers
Depends on:
Blocks:
 
 
Reported: 2012-11-29 11:59 UTC by Martin Pitt
Modified: 2012-11-29 12:16 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
reproducer (280 bytes, text/x-python)
2012-11-29 11:59 UTC, Martin Pitt 		Details

Description Martin Pitt 2012-11-29 11:59:10 UTC 
Created attachment 230175 [details]
reproducer

When running with python3.3-dbg or python2.7-dbg, the test case fails with a segfault in test_gobject.TestContextManagers.test_freeze_notify_context().

However, this is a red herring, the real cause seems to be a refcounting issue in default values. Attached script is a minimal reproducer that I found.
Comment 1 Martin Pitt 2012-11-29 12:08:29 UTC 
For the record, this also is the cause of the segfault that I see on ARM (without the -dbg variant), and possibly the crashes on several of the Debian autobuilders.
Comment 2 Martin Pitt 2012-11-29 12:16:50 UTC 
This was way easier than I thought, fixed in

http://git.gnome.org/browse/pygobject/commit/?id=a107c928ef

This does not affect 3.4, as GVariant properties are not supported there yet (they got introduced in 78f49e6253500)