Segmentation fault (core dumped)

[mtbadakhshan]

When I want to run the following command, a black screen appears and closes. Then, the terminal shows Segmentation fault (core dumped) error.
The command:
python2 brainworkshop.pyw
The result of the pip2 list command is:

Package      Version
------------ -------
folder-color 0.0.86
pip          20.3.4
pyglet       1.5.15
PyGObject    3.36.0
setuptools   44.1.0
urllib3      1.26.4
wheel        0.34.2

I have also installed "AVbin" from here. And I can see the the installed OpenGL version using glxinfo | grep "OpenGL version" command. The result is:
OpenGL version string: 4.6.0 NVIDIA 450.102.04

[xantares]

I cannot reproduce, what platform is this ? windows ?

[veqqq]

I got this on linux mint, with python2 and python2.7

[bookooodoy]

same issue here, valgrind returns gibberish that I don't understand

valgrind python2 brainworkshop.pyw

==7499== Process terminating with default action of signal 2 (SIGINT)
==7499== at 0x4A04117: __futex_abstimed_wait_common64 (futex-internal.c:57)
==7499== by 0x4A04117: __futex_abstimed_wait_common (futex-internal.c:87)
==7499== by 0x4A04117: __futex_abstimed_wait_cancelable64 (futex-internal.c:139)
==7499== by 0x4A0FC77: __new_sem_wait_slow64.constprop.0 (sem_waitcommon.c:183)
==7499== by 0x8BAB154: ??? (in /usr/lib/x86_64-linux-gnu/libopenal.so.1.19.1)
==7499== by 0x8BDEC8A: ??? (in /usr/lib/x86_64-linux-gnu/libopenal.so.1.19.1)
==7499== by 0x4A07AC2: start_thread (pthread_create.c:442)
==7499== by 0x4A98A03: clone (clone.S:100)
==7499==
==7499== HEAP SUMMARY:
==7499== in use at exit: 29,797,672 bytes in 22,155 blocks
==7499== total heap usage: 169,750 allocs, 147,595 frees, 701,004,226 bytes allocated
==7499==
==7499== LEAK SUMMARY:
==7499== definitely lost: 7,860 bytes in 283 blocks
==7499== indirectly lost: 1,309,293 bytes in 148 blocks
==7499== possibly lost: 822,048 bytes in 1,073 blocks
==7499== still reachable: 27,654,663 bytes in 20,612 blocks
==7499== suppressed: 0 bytes in 0 blocks
==7499== Rerun with --leak-check=full to see details of leaked memory
==7499==
==7499== Use --track-origins=yes to see where uninitialised values come from
==7499== For lists of detected and suppressed errors, rerun with: -s
==7499== ERROR SUMMARY: 19066 errors from 155 contexts (suppressed: 0 from 0)

python2 --version
Python 2.7.18

anyone managed to fix this issue ?

[xantares]

maybe you could try python>3.x ?