[Dot] Loop in calculation?

[GadgetSteve]

Ported Issue from Mantis Original ID: 41 Reported By: Wouter Slegers

SEVERITY: MAJOR Submitted: 2002-04-25 08:04:07

OS: X86-UNIX-OPENBSD 3.0-STABLE

VERSION: 1.8.4

DESCRIPTION

Calculation of a graph of approx 175 nodes and 2500 edges takes 150+ MB of memory and was manually aborted after 600+ CPUseconds (realworldtime due to thrashing: more then a week). Input is a graph generated from spidering a website. Reducing the amount of edges by removing all duplicate edges between two nodes, did not help. I haven't yet been able to find what exactly triggers this, so I'm afraid I'm unable to reduce the input file further.

[ellson]

At some graph complexity, finite time, memory, cpu, dot will be unable to complete .. there are no guarantees, but if the code is just looping without any progress then it could be a bug.

Also, bitmap outputs are definite memory hogs for large graphs. Maybe try a vector output like: -Tsvg or -Tps.

Please provide a test graph and exact command line.

Without further info we will close this 2002 bug.

[ Question for GadgetSteve: does this response go to Wouter Slegers, or just to you? ]

[GadgetSteve]

@ellson I am afraid that the response will only come to me - as the XML dump of the open tickets only specifies Mantis usernames, (not email addresses), I had no way to link them to github usernames even if that person had a github username. Not unreasonably github will not let me search on the users real name and even though it is a reasonably uncommon name in this case a simple Google returns thousands of prospective matches.

Since there has been no further input from Wouter in 14 years on this issue I think that it is safe to bet that they have either found a workaround, moved to another tool or a new problem.

If you have access to the Mantis username to email address table then it might be an idea to try and arrange an email simply stating that both the development and tracker have moved to github including still open tickets to either all of the addresses in the database simple to do but a lot of emails or if you are prepared to let me have the list I can whip up a python script to email all of the originators email addresses with a link to their ported ticket(s) and a request to either confirm that the issue still exists for them or that it has been resolved by developments since they raised it - possibly with a statement that if they don't either update or close the new ticket within some period then it will be closed for them - the latter option is a bit more work but will be a much smaller mailshot and would probably have the best clear up rate!