|Anonymous | Login||2017-11-24 15:06 EST|
|Main | My View | View Issues | Change Log | Roadmap | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002382||graphviz||Dot||public||2013-10-11 08:18||2014-04-22 20:45|
|Summary||0002382: shortest.c:324: triangulation failed... source point not in any triangle|
|Description||I have the following errors on graph rendering and dot.exe crashes:|
libpath/.\shortest.c:324: triangulation failed
libpath/.\shortest.c:192: source point not in any triangle
Error: in routesplines, Pshortestpath failed
|Steps To Reproduce||Dot file for reproducing (programmatically generated) is attached but we have the problem for many other graphs. Rendering will work if one of the subgraphs containing large number of nodes is removed.|
|Additional Information||Also was reproduced in versions 2.26, 2.30|
|Tags||No tags attached.|
|VERSION||graphviz version 2.34|
|Attached Files||test.dot [^] (77,148 bytes) 2013-10-11 08:18|
|Another init_rank bug|
thank you for informing that you could reproduce the bug in your lab.
Any idea when it can be fixed?
|Unfortunately, I have no idea when this problem may be fixed as we've had a significant change in our work environment of late.|
We would like to add some information on issue 2382
(http://www.graphviz.org/mantisbt/view.php?id=2382 [^]). I created an account,
but I am not allowed to add a comment on this issue. So, I send you this
We observed that this issue occurs in case of labelling edges between nodes
of different clusters. If you remove the label, everything works fine. You
can use labels for small amounts of clusters. With increasing number of
clusters, the exception occurs.
As a work around, we removed the labels for such edges. Actually, we try to
split that edge into two edges (with label) and a new node:
ClusterA:node1 -> ClusterB:node2
ClusterA:node1 -> dummyNode (outside of ClusterA and ClusterB) ->
If you are interested, we can send you the results of this experiment.
We hope that our information will help you to find the bug.
Please feel free to contact me in the case of any question.
|I just submitted a similar crash for a graph with 7 clusters (of 2 or 3 nodes each), around 25 nodes, and 159 arcs (bug 0002443). By deleting some of the clusters, I can get it to run with as many as 5 clusters and crash with as few as 1, so it's not the case that small numbers of clusters makes it work. (Also not true that only arcs from one cluster to another cause it to crash, as the single-cluster case doesn't have any such arcs). The suggestion about the labels seems like a fruitful approach that might lead to a workaround, though - I'll have to see if a version of the graph without labels crashes.|
Removing all the arc labels from my 7 cluster graph worked. Removing just the cluster->cluster arc labels from a closely related graph didn't (that graph was using lhead/ltail to get cluster arcs to originate on their bounding boxes, and had moved all iter-cluster arcs to the representative node of each cluster, so it was a little easier for me to identify cluster->cluster arcs in that graph).
Good workaround about removing the arc labels, though.
|2013-10-11 08:18||conquest_us||New Issue|
|2013-10-11 08:18||conquest_us||File Added: test.dot|
|2013-10-11 13:46||erg||Note Added: 0000565|
|2013-10-16 08:17||conquest_us||Note Added: 0000569|
|2013-10-30 13:57||erg||Note Added: 0000591|
|2014-02-18 13:43||erg||Note Added: 0000688|
|2014-04-22 20:21||dewtell||Note Added: 0000730|
|2014-04-22 20:45||dewtell||Note Added: 0000731|
|MantisBT 1.2.5[^] Copyright © 2000 - 2011 MantisBT Group|