# Python shell segmentation fault after exiting when importing pygplates

**URL:** https://discourse.gplates.org/t/python-shell-segmentation-fault-after-exiting-when-importing-pygplates/487
**Category:** Bug Reports
**Created:** [3 March 2022 03:20 UTC](https://discourse.gplates.org/t/python-shell-segmentation-fault-after-exiting-when-importing-pygplates/487 "2022-03-03T03:20:01Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![john.cannon](https://discourse.gplates.org/letter_avatar_proxy/v4/letter/j/3e96dc/32.png) [@john.cannon](https://discourse.gplates.org/u/john.cannon)
#### Post date: [3 March 2022 04:01 UTC](https://discourse.gplates.org/t/python-shell-segmentation-fault-after-exiting-when-importing-pygplates/487/2 "2022-03-03T04:01:10Z")

</div>

Hi vinnie,

It’s an issue with version 3.9 of Python (when using pyGPlates). As you noted the seg fault happens on exiting. I’m currently looking into it and will let you know when it’s fixed (it looks to be a reference count issue in a boost-python object somewhere).

In regard to the warning messages you mentioned, there’s more recent source code (revision 33) mentioned in [this post](https://discourse.gplates.org/t/splitting-isochrons-bisected-by-future-ridge-pygplates/449/8) but it won’t fix the above seg fault.

---

_[View the full topic](https://discourse.gplates.org/t/python-shell-segmentation-fault-after-exiting-when-importing-pygplates/487)._