This repository has been archived by the owner on Nov 17, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6.8k
Custom-Op Bug when using multiple custom-ops #4521
Comments
|
os.environ["MXNET_CPU_WORKER_NTHREADS"] = "4" |
Merged
It has been fixed by #4528 |
Need some help, Thank you! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I found that when using multiple output custom-ops, the program got stuck. It seems that the engine is suffering from the deadlock. This problem will occur when the custom-op contains the codes like `mx.nd.xx( xx ).asnumpy()'. This problem does not occur when using NaiveEngine.
I have written an example to reproduce this bug. You can put this file on the path of 'exmple/numpy-ops' and then run it. If we add line 15, the program will get stuck. Otherwise it works fine.
MXNet version: test two versions.
The text was updated successfully, but these errors were encountered: