Bug 1199254 - neato crashes with "out of memory" and segv
Summary: neato crashes with "out of memory" and segv
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: graphviz
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaroslav Škarvada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-05 18:21 UTC by Zbigniew Jędrzejewski-Szmek
Modified: 2015-12-02 17:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-02 09:48:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
another crasher (390.40 KB, text/plain)
2015-03-05 18:42 UTC, Zbigniew Jędrzejewski-Szmek
no flags Details

Description Zbigniew Jędrzejewski-Szmek 2015-03-05 18:21:45 UTC
Description of problem:
With the attached file:
$ neato -Tpng dependencies.dot > dependencies.png
out of memory
Segmentation fault (core dumped)

Version-Release number of selected component (if applicable):
graphviz-2.34.0-10.fc20.x86_64

How reproducible:
100%

Comment 1 Zbigniew Jędrzejewski-Szmek 2015-03-05 18:42:53 UTC
Created attachment 998505 [details]
another crasher

Another one:

$ dot -Tx11 dependencies2000.dot
segmentation fault (core dumped)

Comment 2 Jaroslav Škarvada 2015-03-09 15:11:19 UTC
Same problem on f21, changing version to f21 and reporting upstream.

Comment 3 Jaroslav Škarvada 2015-03-09 15:14:10 UTC
But the following works:
$ neato -Tpng dependencies2000.dot dependencies2000.png

machine with 8 GB RAM.

Comment 4 Jaroslav Škarvada 2015-03-09 15:27:19 UTC
Upstream ticket:
http://www.graphviz.org/mantisbt/view.php?id=2528

Comment 5 Jaroslav Škarvada 2015-03-09 15:46:45 UTC
It seems it runs out of stack space during recursion.

Comment 6 Jaroslav Škarvada 2015-03-09 16:07:21 UTC
Probably 8 MB stack isn't enough for recursion in such huge task.

With 'setlimit -s unlimited' it runs, runs and runs. Currently I am not sure whether it is doing useful work or just simply cycling. I will let it run for a while and let's see.

The limits and aborts are glibc business. I don't know whether we can easily treat this (without performance penalty), i.e. check whether the task requires more resources than available and correctly exit.

Comment 7 Fedora End Of Life 2015-11-04 15:39:16 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Fedora End Of Life 2015-12-02 09:48:08 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.