|Anonymous | Login||2017-11-23 09:46 EST|
|Main | My View | View Issues | Change Log | Roadmap | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002461||graphviz||Dot||public||2014-05-29 08:26||2014-05-29 12:29|
|Summary||0002461: dot segfaults (2.26.3-15+b1)|
|Description||I have this large dot-file that I would like to convert to svg.|
When doing so, dot segfaults.
/usr/bin/dot -Tsvg -o linkernbug.svg linkern.dot
Dot file used: http://keetweej.vanheusden.com/linkern.dot [^]
Tried to build a debug version of graphviz but this failed on some ruby file missing or so so I gave up.
Did a gdb run anyway and saw thousands (> 10000) stackframes in /usr/lib/graphviz/libgvplugin_dot_layout.so.6
#10503 0x00007ffff3aa1bfb in ?? () from /usr/lib/graphviz/libgvplugin_dot_layout.so.6
#10504 0x00007ffff3aa1bfb in ?? () from /usr/lib/graphviz/libgvplugin_dot_layout.so.6
#10505 0x00007ffff3aa1bfb in ?? () from /usr/lib/graphviz/libgvplugin_dot_layout.so.6
|Tags||No tags attached.|
I don't think this is SVG related.
using "dot - graphviz version 2.39.20140529.0445 (20140529.0445)"
also hangs on this graph with 100% cpu.
No sign of memory growth.
There are two problems. The crash is caused by a stack overflow in the recursively-written search_component function in decomp.c. When the graph is extended with dummy nodes, there are 4618005 nodes. The function needs to be rewritten using iteration, but this graph is probably too big for dot anyway.
You won't see this problem if you are using dot with cgraph, as the other problem is happening during cleanup1 after ranking. I'm not sure what is happening here yet. The cgraph version is quadratic in the edges, of which there are 71889, so it could just be taking a LONG time.
|2014-05-29 08:26||flok||New Issue|
|2014-05-29 09:40||ellson||Note Added: 0000750|
|2014-05-29 12:29||erg||Note Added: 0000751|
|MantisBT 1.2.5[^] Copyright © 2000 - 2011 MantisBT Group|