-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
Error when importing diffeqpy parallely in large number of sub-processes. #98
Comments
Sounds like a pyjulia problem. I'm not sure we can solve it at this repo. |
@ChrisRackauckas I tried an experiment where I only imported the |
Is it dying because you run out of memory? That would be a good way to diagnose that 😅 |
@ChrisRackauckas No, the workstation I am using has 128 GB of memory. And only about 50% memory utilization is there at the time of the error. |
@tkf might have an idea. |
Maybe you are using fork? See: JuliaPy/pyjulia#448 (comment) |
Has this issue been resolved? I am trying to use the diffeqpy package in a general fitting software (PyBNF) but without the dask compatibility I am getting nowhere. If I try to use julia prior to submitting the jobs I get a error trying to pickle pycall objects. If I import julia in the function, it is extremely slow and prone to crashing. |
@JacobNeumann88 No my issue is not resolved. So in my application, I am limited to using less than 50 instances of diffeqpy. I have not used it with Dask.
|
Was a PyJulia thing, now gone with PythonCall. |
I have a program that spawns a large number of sub-processes and imports
diffeqpy
within each sub-process using:from diffeqpy import ode
It works fine when the number of sub-processes is less than 75. But above that I am getting the following error:
"exception: access violation writing 0x000001EC9127C000"
I am using the following:
diffeqpy: 1.2.0
pyjulia: 0.5.7
Julia 1.5.3, 1.6, 1.7
I have a feeling this could be a pyjulia problem. But I just wanted to check here to see if anyone else has encountered it.
The text was updated successfully, but these errors were encountered: