Segmentation fault when calculating eigenvector centrality

Bug #739954 reported by Amy Yu
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
igraph
Fix Released
High
Tamás Nepusz

Bug Description

Python 2.6.5 (r265:79063, Apr 16 2010, 13:57:41)
In [1]: import igraph
In [2]: g = igraph.Graph([(0,1), (0,2), (2,3), (3,4), (4,2), (2,5), (5,0), (6,3), (5,6)])
In [3]: g.eigenvector_centrality()
Segmentation fault (core dumped)

I get a segmentation fault error whenever I attempt to calculate eigenvector centrality using igraph. I am using version 0.5.4.

Revision history for this message
Tamás Nepusz (ntamas) wrote :

What OS are you using and how did you install igraph? The reason why I am asking is because it works for me with igraph 0.5.4 (compiled fresh from the source code):

tamas@keszeg:~/bzr/igraph/0.5-main/build $ igraph
No configuration file, using defaults
igraph 0.5.4 running inside Python 2.6.6 (r266:84292, Sep 15 2010, 16:22:56)
Type "copyright", "credits" or "license" for more information.

IPython 0.10 -- An enhanced Interactive Python.
? -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help -> Python's own help system.
object? -> Details about 'object'. ?object also works, ?? prints more.

In [1]: g=Graph([(0,1), (0,2), (2,3), (3,4), (4,2), (2,5), (5,0), (6,3), (5,6)])
In [2]: g.eigenvector_centrality()
Out[2]:
[0.71119954501079996,
 0.24860112203602616,
 1.0,
 0.75139887796397364,
 0.6122047310756773,
 0.78600269906125164,
 0.53740157702522562]

Revision history for this message
Amy Yu (amyzhao-yu) wrote : Re: [Bug 739954] Re: Segmentation fault when calculating eigenvector centrality

Hi Tamás,

Thanks for the fast response! I am using Ubuntu 10.04 LTS. I installed
igraph by doing:

sudo add-apt-repository ppa:igraph/ppa

sudo aptitude update
sudo aptitude install python-igraph

I just tried reinstalling using the above commands but I am still
getting the segmentation fault. Let me know if you have any
suggestions!

Thanks,

Amy

<http://igraph.wikidot.com/installing-python-igraph-on-linux>

On Tue, Mar 22, 2011 at 5:50 AM, Tamás Nepusz <email address hidden> wrote:

> What OS are you using and how did you install igraph? The reason why I
> am asking is because it works for me with igraph 0.5.4 (compiled fresh
> from the source code):
>
> tamas@keszeg:~/bzr/igraph/0.5-main/build $ igraph
> No configuration file, using defaults
> igraph 0.5.4 running inside Python 2.6.6 (r266:84292, Sep 15 2010,
> 16:22:56)
> Type "copyright", "credits" or "license" for more information.
>
> IPython 0.10 -- An enhanced Interactive Python.
> ? -> Introduction and overview of IPython's features.
> %quickref -> Quick reference.
> help -> Python's own help system.
> object? -> Details about 'object'. ?object also works, ?? prints more.
>
> In [1]: g=Graph([(0,1), (0,2), (2,3), (3,4), (4,2), (2,5), (5,0), (6,3),
> (5,6)])
> In [2]: g.eigenvector_centrality()
> Out[2]:
> [0.71119954501079996,
> 0.24860112203602616,
> 1.0,
> 0.75139887796397364,
> 0.6122047310756773,
> 0.78600269906125164,
> 0.53740157702522562]
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/739954
>
> Title:
> Segmentation fault when calculating eigenvector centrality
>
> Status in The igraph library:
> New
>
> Bug description:
> Python 2.6.5 (r265:79063, Apr 16 2010, 13:57:41)
> In [1]: import igraph
> In [2]: g = igraph.Graph([(0,1), (0,2), (2,3), (3,4), (4,2), (2,5), (5,0),
> (6,3), (5,6)])
> In [3]: g.eigenvector_centrality()
> Segmentation fault (core dumped)
>
> I get a segmentation fault error whenever I attempt to calculate
> eigenvector centrality using igraph. I am using version 0.5.4.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/igraph/+bug/739954/+subscribe
>

--
-Amy

Revision history for this message
Tamás Nepusz (ntamas) wrote :

Is it a 64-bit or a 32-bit system?

Revision history for this message
Tamás Nepusz (ntamas) wrote :

Seems to happen on 64-bit systems only; I'll try to push out a new version of the package that should work. It will take a couple of hours, though.

Changed in igraph:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Tamás Nepusz (ntamas)
Revision history for this message
Tamás Nepusz (ntamas) wrote :

The fixed package is currently being re-built by Launchpad. If you wish, I can send you a package built on my own machine so you can try it. Just drop me a mail.

Revision history for this message
Amy Yu (amyzhao-yu) wrote :

Sure! Do I install it the same way?

Via mobile

On Mar 22, 2011, at 12:20 PM, "Tamás Nepusz" <email address hidden> wrote:

> The fixed package is currently being re-built by Launchpad. If you wish,
> I can send you a package built on my own machine so you can try it. Just
> drop me a mail.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/739954
>
> Title:
> Segmentation fault when calculating eigenvector centrality
>
> Status in The igraph library:
> Confirmed
>
> Bug description:
> Python 2.6.5 (r265:79063, Apr 16 2010, 13:57:41)
> In [1]: import igraph
> In [2]: g = igraph.Graph([(0,1), (0,2), (2,3), (3,4), (4,2), (2,5), (5,0), (6,3), (5,6)])
> In [3]: g.eigenvector_centrality()
> Segmentation fault (core dumped)
>
> I get a segmentation fault error whenever I attempt to calculate
> eigenvector centrality using igraph. I am using version 0.5.4.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/igraph/+bug/739954/+subscribe

Revision history for this message
Tamás Nepusz (ntamas) wrote :

For the record: Amy wrote that the problem is solved with the new Debian package. It was an issue with the usage of an external ARPACK implementation on a 64-bit machine - this will be fixed permanently in the next release. The 0.6-arpack branch was already merged into trunk.

Changed in igraph:
status: Confirmed → Fix Committed
Revision history for this message
Jordi Torrents (jtorrents) wrote :

Hi Tamas,

I've just installed the igraph python packages from PPA Launchpad (build 5 weeks ago) and it seems that the bug is still there:

jtorrents@jupiter:~$ igraph
No configuration file, using defaults
igraph 0.5.4 running inside Python 2.6.6 (r266:84292, Dec 26 2010, 22:31:48)
Type "copyright", "credits" or "license" for more information.

IPython 0.10 -- An enhanced Interactive Python.
? -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help -> Python's own help system.
object? -> Details about 'object'. ?object also works, ?? prints more.

In [1]: g=Graph([(0,1), (0,2), (2,3), (3,4), (4,2), (2,5), (5,0), (6,3), (5,6)])
In [2]: g.eigenvector_centrality()
Segmentation fault
jtorrents@jupiter:~$

I'm using Debian Squeeze 64bits (amd64) and I have used the maverik target on PPA. In a system with the same configuration but with 32 bits (ie Debian stable and igraph installed from maverik target on PPA) seems to work fine.

Thanks

Revision history for this message
Jordi Torrents (jtorrents) wrote :

Hi again,

It seems that the problem is that the build with Tamas' fix (libigraph0 0.5.4-4) is only available for Lucid and not for Maverick. Installing libigraph0 0.5.4-4 solved the segfault in my system (Debian Squeeze amd64).

Salut!

Revision history for this message
Tamás Nepusz (ntamas) wrote :

Yes, sorry, I forgot to copy the new packages from the lucid repo to maverick & natty. This has to be done manually after the build finishes, and sometimes I forget this. Thanks for the heads up.

Tamás Nepusz (ntamas)
Changed in igraph:
status: Fix Committed → Fix Released
Revision history for this message
Gábor Csárdi (gabor.csardi) wrote : Continue on github

The development of igraph has moved to github, so please do not comment on this bug here. You are of course welcome to comment on github, here:
https://github.com/igraph/igraph/issues/87

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.