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
Kernel Restart - Incompatibility between nx.draw and utils_tf.data_dicts_to_graphs_tuple #124
Comments
I have not observed this, not sure if @Mistobaan did. Are you running on your own kernel, or on Google Colaboratory? |
In my experience that is usually an out of memory case. Check the system logs if you are running on Colab. |
Hi, thanks. I'm running on GCP Notebook with 15GB RAM. GCP logs show: Aug 12 21:12:02 ... bash[1278]: OMP: Error #15: Initializing libiomp5.so, but found libomp.so already initialized. |
I think the answer is printed by your logs:
|
@Mistobaan - yes, I’ve used that as a workaround but wondered if there was a better option? |
Get a bigger machine with more memory? Can you replicate the problem into a colab and post the link to the colab? make sure you set the share permissions. |
Upgrading to GCP Notebook Tensorflow 2.3 (from 2.2.0) resolved the issue. |
Hi.
I'm trying to use nx.draw and utils_tf.data_dicts_to_graphs_tuple in the same TF2 notebook.
Whichever is executed second seems to cause a kernel restart in the notebook which i can't explain. Importing networkx is fine as long as nx.draw is not run.
@Mistobaan - I get this behaviour on your very helpful TF2 version of graph_nets_basic tutorial.
Michael.
The text was updated successfully, but these errors were encountered: