-
Notifications
You must be signed in to change notification settings - Fork 74.2k
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
CUDA cannot create more than one session #19482
Comments
I use a Jetson TX2, so its quite difficult to use a cpu only build (takes a lot of time). I'm concerned since I do not know how to fill a proper bug report. How to debug programs with CUDA and CUdnn ? |
I had not used or seen multiple sessions in a script but indeed it happens and there as an issues resolved a long time ago. I would test the code on a regular GPU just to rule in or out Jetson being the issue. We do not have a Jetson TX2 or TX setup in our area. I would also wrap the session in a with.device just to make sure it is going where you want, but that is likely not needed really. If there was a CUDA issue I would expect to see a CUDA error but expectation does not always match reality. Here is the multi-session example I found while looking for issues. They call run before starting the next session but I do not see why that would matter. For debugging CUDA, I do not have direct knowledge. You could try the tfdebugging as a starting point. https://www.tensorflow.org/programmers_guide/debugger I also do not have experience with it. Huge help right? That is where I would start. Finding out it is a Jetson specific issue would be my first thought, then going from there. |
I'm now getting error on the CUDA runtime implicit initialization on GPU
|
@Davidnet There is likely not much I can debug. I would suggest the following:
Finally, keep in mind this is not a help desk and mostly it is about giving you ideas. In the case of the Jetson even more so as we do no have those sitting around like we do GPUs or CPUs on our local machines. Do not read this as not wanting to help. Everyone wants to help and the biggest frustration is not having enough information. |
Nagging Assignee @skye: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly. |
Please go to Stack Overflow for help and support:
https://stackoverflow.com/questions/tagged/tensorflow
If you open a GitHub issue, here is our policy:
Here's why we have that policy: TensorFlow developers respond to issues. We want to focus on work that benefits the whole community, e.g., fixing bugs and adding features. Support only helps individuals. GitHub also notifies thousands of people when issues are filed. We want them to see you communicating an interesting problem, rather than being redirected to Stack Overflow.
System information
source
1.8
2.7
0.13
5.4.0
9.0/7.0
Tegra x2
config = tf.ConfigProto()
config.gpu_options.per_process_gpu_memory_fraction = 0.4 # I have also tried with allow memory growth
sess1 = tf.Session(config=config)
sess2=tf.Session(config=config) # Cannot create the session
You can collect some of this information using our environment capture script:
https://github.com/tensorflow/tensorflow/tree/master/tools/tf_env_collect.sh
You can obtain the TensorFlow version with
python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
Describe the problem
Describe the problem clearly here. Be sure to convey here why it's a bug in TensorFlow or a feature request.
I have a Jetson TX2 with updated drivers and the last jetpack provided by Nvidia, I have built tensorflow (r.1.5 and r.18) and I'm not able to create more than one session, I can execute operations and everything with only one session, but once I create a new session, I encounter that tensorflow cannot create a new session, which I suspect is Nvidia fault, but the error is not that informative:
Is there any way I can get more information about the cuda error or status? So I can complement my bug report?
Thanks
Source code / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached. Try to provide a reproducible test case that is the bare minimum necessary to generate the problem.
The text was updated successfully, but these errors were encountered: