Message387036
| Author | pablogsal |
|---|---|
| Recipients | amaury.forgeotdarc, arigo, ghaering, iritkatriel, jcea, lkraav, pablogsal, pitrou, pxd, vstinner |
| Date | 2021-02-15.18:02:33 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1613412153.8.0.778410493488.issue15108@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
> If the GIL is released before the tuple is fully populated and something access to this tuple via the GC (ex: gc.get_objects()), accessing the tuple can crash, especially in the Python land (for example, repr(the_tuple) is likely to crash). It can happen even without releasing the GIL: A new tuple is created, then some other object is created using the CAPI, the gc runs, the callback triggers (or the tuplevisit method is invoked) and then kaboom |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2021-02-15 18:02:33 | pablogsal | set | recipients: + pablogsal, arigo, jcea, ghaering, amaury.forgeotdarc, pitrou, vstinner, lkraav, pxd, iritkatriel |
| 2021-02-15 18:02:33 | pablogsal | set | messageid: <1613412153.8.0.778410493488.issue15108@roundup.psfhosted.org> |
| 2021-02-15 18:02:33 | pablogsal | link | issue15108 messages |
| 2021-02-15 18:02:33 | pablogsal | create | |