Re: [OMPI users] Segfault in mpi-java

2015-02-07 Thread Jeff Squyres (jsquyres)
We'll follow up on this github issue. Alexander -- thanks for the bug report. If you'd like to follow the progress of this issue, comment on https://github.com/open-mpi/ompi/issues/369. > On Feb 1, 2015, at 5:08 PM, Oscar Vega-Gisbert wrote: > > Hi, > > I created an issue with a simplified

Re: [OMPI users] Segfault in mpi-java

2015-02-01 Thread Oscar Vega-Gisbert
Hi, I created an issue with a simplified example: https://github.com/open-mpi/ompi/issues/369 Regards, Oscar El 25/01/15 a las 19:36, Oscar Vega-Gisbert escribió: Hi, I also reproduce this behaviour. But I think this crash is not related with garbage collector. Java is much better than you

Re: [OMPI users] Segfault in mpi-java

2015-01-25 Thread Oscar Vega-Gisbert
Hi, I also reproduce this behaviour. But I think this crash is not related with garbage collector. Java is much better than you think. May be MPI corrupts the Java runtime heap. Regards, Oscar El 22/01/15 a las 08:07, Gilles Gouaillardet escribió: Alexander, i was able to reproduce this be

Re: [OMPI users] Segfault in mpi-java

2015-01-22 Thread Gilles Gouaillardet
Alexander, i was able to reproduce this behaviour. basically, bad things happen when the garbage collector is invoked ... i was even able to reproduce some crashes (but that happen at random stages) very early in the code by manually inserting calls to the garbage collector (e.g. System.gc();) C

[OMPI users] Segfault in mpi-java

2015-01-18 Thread Alexander Daryin
Hi I am using Java MPI bindings and periodically get fatal erros. This is illustrated by the following model Java program. import mpi.MPI; import mpi.MPIException; import mpi.Prequest; import mpi.Request; import mpi.Status; import java.nio.ByteBuffer; import java.util.Random; public class Test