Graph creation fails: out of memory error

Bug #524534 reported by Jack Hargett
22
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Facebook Friends Graph
Confirmed
Undecided
Unassigned

Bug Description

Hi,

I'm getting the following error about 4-5 minutes into the graph creation routine:

Exception in thread Thread-2:
Traceback (most recent call last):
  File "/usr/lib/python2.6/threading.py", line 525, in __bootstrap_inner
    self.run()
  File "fbfriendsgraph.py", line 59, in run
    written = self.graph.write_png(self.filename, prog = 'neato')
  File "/usr/lib/pymodules/python2.6/pydot.py", line 1602, in <lambda>
    lambda path, f=frmt, prog=self.prog : self.write(path, format=f, prog=prog))
  File "/usr/lib/pymodules/python2.6/pydot.py", line 1696, in write
    dot_fd.write(self.create(prog, format))
  File "/usr/lib/pymodules/python2.6/pydot.py", line 1796, in create
    status, stderr_output) )
InvocationException: Program terminated with status: -11. stderr follows: neato: failure to create cairo surface: out of memory

I'm running ubuntu 9.10 (32-bit), AMD Athlon 64 (4000), 3GB RAM, and plenty of free disk / swap.

Any help is greatly appreciated!

Regards,
Jack

Revision history for this message
Kamran Riaz Khan (inspirated) wrote :

Thanks for taking the time to report the bug. However, AFAIK this issue is purely dependent on your machine specs and the complexity of your graph. I have ~300 friends and the graph generation does cripple down my 2 GB RAM/1.8 C2D processor. I'm pretty sure 500+ friends would not work in my case either. For the time being, I'm marking the bug as invalid. However if you think you have a reasonable (technically speaking, nothing to do with social interpretation ;) ) number of friends, feel free to reopen.

Changed in fbfriendsgraph:
status: New → Invalid
Revision history for this message
Jack Hargett (njhargett) wrote : Re: [Bug 524534] Re: Graph creation fails: out of memory error

Hi there... I just downloaded the lasted release, and the issue I
reported no longer exists! I have successfully generated graphs with
this release, where as I could not with the prior release. I'm not sure
what changes were coded, but just wanted to let you know this issue no
longer exists for me.

Thank you!

Jack

Kamran Riaz Khan wrote:
> Thanks for taking the time to report the bug. However, AFAIK this issue
> is purely dependent on your machine specs and the complexity of your
> graph. I have ~300 friends and the graph generation does cripple down my
> 2 GB RAM/1.8 C2D processor. I'm pretty sure 500+ friends would not work
> in my case either. For the time being, I'm marking the bug as invalid.
> However if you think you have a reasonable (technically speaking,
> nothing to do with social interpretation ;) ) number of friends, feel
> free to reopen.
>
> ** Changed in: fbfriendsgraph
> Status: New => Invalid
>
>

Revision history for this message
giorgio130 (gm89) wrote :

~300 friends, 4 gb ram, 2.53 C2D processor, same error as above with last revision. Should this be reopened?

Revision history for this message
Kamran Riaz Khan (inspirated) wrote :

Which version of graphviz are you using?

Revision history for this message
kanor (kanor) wrote :

same error here, 373 friends 24 (!!!) gb memory
graphviz 2.20.2-8ubuntu3
10.04

Changed in fbfriendsgraph:
status: Invalid → Confirmed
Revision history for this message
Rafał (raafal) wrote :

same error, 358 friends, 6 GB memory
graphviz 2.26.3-4
10.10

Revision history for this message
Philipp Zöchner (zornp) wrote :

got the exact same error with < 300 friends.
4 GB RAM
using the latest version from the branch. 4th revision.
11.04 beta

Revision history for this message
Philipp Zöchner (zornp) wrote :

my bad.. the last line differs!

InvocationException: Program terminated with status: -11. stderr follows: neato: graph is too large for cairo-renderer bitmaps. Scaling by 0.607089 to fit
neato: failure to create cairo surface: out of memory

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers