This is a duplicate of T71908, closing this report in favour of that one

Awesome.
Thankyou everyone.
My first ever contribution to blender is in! Yay! \o/
:D

This new diff should include all the recommended changes,
that python string conversion function did indeed work, the code looks much cleaner now :)

@Campbell Barton (campbellbarton) Thanks for the review, some helpful suggestions :)

Better link, now that I've figured out how phabricator works 😁
https://developer.blender.org/D8457

@Sybren A. Stüvel (sybren) After a little bit of reading the python C api docs, I've found it to be fairly easy to generate a python backtrace upon a segfault. And given that it's easy to catch a segfault (in linux at least, I haven't tried windows) without doing anything hacky, I have been able to get blender to provide a python backtrace when python code causes a segfault.

I don't think this is an invalid bug report.
Sure it's a known issue, and it's documented, but it's not likely that any user is going to find that documentation upon encountering what appears to be a random segfault.