Don't crash on multiple calls to GObject.Value.__del__. See !66dd2a6c36b2a8960d05b81d46fb6b1cc063222497
| commit | dd2a6c36b2a8960d05b81d46fb6b1cc063222497 | |
| author | Christoph Reiter <reiter.christoph@gmail.com> | |
| Fri, 4 May 2018 19:29:13 +0000 (4 21:29 +0200) | ||
| committer | Christoph Reiter <reiter.christoph@gmail.com> | |
| Fri, 4 May 2018 19:35:02 +0000 (4 21:35 +0200) | ||
| tree | 4338f98aa096ed6a7e0eca2a8020dd5981aca4ef | treesnapshot (tar.gz zip) |
| parent | b4417a4432fe96ce545ecaf61fc7d2d745020614 | commitdiff |
Don't crash on multiple calls to GObject.Value.__del__. See !66
After chaining up accessing anything on the instance will crash like
accessing self.g_type in this case. Guard against that by exposing if the
wrapped boxed is still there.
Ideally we shouldn't invalidate the object in __del__, but various
things depend on it atm. For another time..
After chaining up accessing anything on the instance will crash like
accessing self.g_type in this case. Guard against that by exposing if the
wrapped boxed is still there.
Ideally we shouldn't invalidate the object in __del__, but various
things depend on it atm. For another time..
| gi/overrides/GObject.py | diffblobblamehistory | |
| gi/pygi-boxed.c | diffblobblamehistory | |
| tests/test_gobject.py | diffblobblamehistory |