-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
exit with code -1073741819 (0xC0000005) #271
Comments
I suspect PythonMonkey is segfaulting here, likely due to a GC root that isn't being persisted properly. What do you think, @caleb-distributive ? |
So this means probably that we tried to access a page which isn't mapped into the process address space. The most likely address for that is NULL - we're probably de-referencing a NULL ptr the second time through. |
I just noticed you are on Python 3.8, @caleb-distributive are there important things that don't work under 3.9 that could affect this user? |
@hjdhnx please provide the most minimal possible example with all files needed to reproduce |
see Standalone code to reproduce the issue |
@hjdhnx |
I'm getting the same issue on Windows 11 with Python 3.12.2, pythonmonkey 0.7.1, 0.8.0, 0.8.1.dev3+5fc6ce0. Python just crashes when I try to Is there anything I can do to help you debug this further? |
Issue type
Bug
How did you install PythonMonkey?
Installed from pip
https://nightly.pythonmonkey.io/pythonmonkey/
OS platform and distribution
windows11
Python version (
python --version
)3.8.8 64bit
PythonMonkey version (
pip show pythonmonkey
)0.3.1.dev83+b2be8c9
Bug Description
When I use PythonMonkey in interface services, such as FastAPI, as long as I load a JavaScript module and use it as a Python variable, when I call the method of this variable again, the entire interface backend service process will be forced to exit
look here
Standalone code to reproduce the issue
drpy.js
drpy_run.py
main.py
drpy_run.py tests ok,but main.py tests error
when we view this http api, this bug happend
http://127.0.0.1:8000
@wesgarland @philippedistributive
Relevant log output or backtrace
No response
Additional info if applicable
No response
What branch of PythonMonkey were you developing on? (If applicable)
No response
The text was updated successfully, but these errors were encountered: