esimov / pigo

Fast face detection, pupil/eyes localization and facial landmark points detection library in pure Go.
MIT License
4.37k stars 309 forks source link

Got exit code 1073741819 (0xC0000005) from python demo #58

Closed xinxin8816 closed 1 year ago

xinxin8816 commented 2 years ago

Hi there, I try to exec demo with Python 3.9 on Windows, sometimes got unexpected exit, with code -1073741819 (0xC0000005) , that err from C shared lib I think, and that because of index out of range usually. I'm not good at Golang and not founded the true reason from code, give me some advice to fix it please, thx.

esimov commented 2 years ago

Can you show me exactly what kind of errors are you getting? Just FYI these demos have been tested on Python2 and OpenCV2 so it might be related to the Python version also on which you are trying to run it.

xinxin8816 commented 2 years ago

Nothing exactly others, just response err code and exit. That err code correlate with out of range in my experience. Python2 may working well, but Python2 has out of date now.

esimov commented 2 years ago

I'm aware about that, only that because I have ported the library to WASM I didn't updated the Python examples to run on Python3. But I have tried it with Python3 and OpenCV4 and sometimes just exited without printing any errors. That's why I asked if you could have shown the errors you got.

xinxin8816 commented 2 years ago
image

Only got this unuseful message, means: Process has been exited, exit code is -1073741819 (0xC0000005)

esimov commented 2 years ago

I have tried on a MacOS with Python 3.9.1 installed and the demos are running, but strangely on Windows in most of the cases the application exits without showing any errors. I was trying to debug it and most probably is related to the data type transfer from Go to Python using ctypes.

xinxin8816 commented 2 years ago

I ran in pycharm with debug mode, and than got exit code. If running in cmd or powershell, that output nothing.

esimov commented 1 year ago

I'm closing this ticket, the issue is fixed now.