Graph visualization failed: GraphDefs failed to reconcile.
See original GitHub issueIn TensorFlow v2, below code can cause GraphDef reconciliation error.
@tf.function
def foo(x):
return x ** 2
with writer.as_default():
tf.summary.trace_on()
foo(1)
foo(2)
tf.summary.trace_export("foo")
Depending on the argument, tf.function
(really, auto-graph) creates ops that are unique within GraphDef but is not globally unique. In the example above, two GraphDefs (on from foo(1)
and another from foo(2)
) will be written out and they can collide badly in names and content.
In such case, instead of showing wrong graph content, TensorBoard throws an error.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:18 (1 by maintainers)
Top Results From Across the Web
Malformed Op graph of custom Keras model
The Conceptual graph is generated, however, the Op graph returns: Error: Malformed GraphDef. I tried some existing suggestions related to ...
Read more >How to visualize graph without training the model using ...
Graph visualization failed. Error: Malformed GraphDef. This can sometimes be caused by a bad network connection or difficulty reconciling ...
Read more >Tensorboard 'Graph Visualization Failed', In Graph Mode
Ask questionsGraph visualization failed: GraphDefs failed to reconcile. In TensorFlow v2, below code can cause GraphDef reconciliation error.
Read more >Unable to login to graph visualization - Page 2 — oracle-tech
Unable to login to graph visualization ... I just had a quick look in the documentation of the Graph Server to make sure...
Read more >Analysis and Visualization of Communication/Computation Patterns ...
4 Graph Visualization of Communication and Computation ... parametrized balance between it and the application's throughput. ... GraphDefs. «extends».
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I was facing this issue as well. Found out that switching the verbose-type from 2 to 1 in the model.fit()-function solved the problem. This might help somebody here, too. Since I’m unsure if this behaviour is intended, I created a issue for it (see here: https://github.com/tensorflow/tensorboard/issues/5745).
any update about this issue? It has been more than one year since the issue was put forward 😢