You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by Alberto Rodriguez <ar...@gmail.com> on 2015/06/02 11:37:02 UTC
Native code error
Hi all,
I've got a bunch of tests that are checking whether my spark process is
able to connect to a mesos cluster. The "happy path" (mesos up & running)
is working fine the problem comes when I'm testing a connection with a
wrong mesos ip then I'm getting the following error:
WARNING: Logging before InitGoogleLogging() is written to STDERR
W0602 11:26:03.549504 13269 sched.cpp:1323]
**************************************************
Scheduler driver bound to loopback interface! Cannot communicate with
remote master(s). You might want to set 'LIBPROCESS_IP' environment
variable to use a routable IP address.
**************************************************
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fcdf32c5660, pid=13125, tid=140517706200832
#
# JRE version: Java(TM) SE Runtime Environment (7.0_75-b13) (build
1.7.0_75-b13)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.75-b04 mixed mode
linux-amd64 compressed oops)
# Problematic frame:
# C [libc.so.6+0x83660] cfree+0x220
#
# Core dump written. Default location:
/home/arodriguez/dev/datavis-master/back/core or core.13125 (max size 50000
kB). To ensure a full core dump, try "ulimit -c unlimited" before starting
Java again
#
# An error report file with more information is saved as:
# /home/arodriguez/dev/datavis-master/back/hs_err_pid13125.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
/bin/sh: línea 1: 13125 Abortado (`core' generado)
/usr/java/jdk1.7.0_75/jre/bin/java
-javaagent:/home/arodriguez/.m2/repository/org/jacoco/org.jacoco.agent/0.7.2.201409121644/org.jacoco.agent-0.$.2.201409121644-runtime.jar=destfile=/home/arodriguez/dev/datavis-master/back/target/jacocoIT.exec
-Xmx1024m -XX:MaxPermSize=256m
-Dlogback.configurationFile=conf/logger/develop.logger.xml
-Djava.security.polic$=conf/java.policy -XX:+HeapDumpOnOutOfMemoryError
org.apache.maven.surefire.booter.ForkedBooter
/home/arodriguez/dev/datavis-master/back/target/surefire/surefire6809257750333050101tmp
/home/arodriguez/dev/datav$s-master/back/target/surefire/surefire_02320528722071658975tmp
Any ideas?
Re: Native code error
Posted by Alberto Rodriguez <ar...@gmail.com>.
Done! Thank you!
2015-06-10 8:52 GMT+02:00 Alex Rukletsov <al...@mesosphere.com>:
> Mark it as a duplicate.
> On 10 Jun 2015 8:21 am, "Alberto Rodriguez" <ar...@gmail.com> wrote:
>
> > Thank you for replying and for opening a ticket. I also added a ticket
> > related to the issue: https://issues.apache.org/jira/browse/MESOS-2820
> > Should I close it?
> >
> > Thank you
> >
> > 2015-06-10 0:29 GMT+02:00 Niklas Nielsen <ni...@mesosphere.io>:
> >
> > > Thanks Alberto - I finally got to look at the trace and added a ticket
> to
> > > track it: https://issues.apache.org/jira/browse/MESOS-2839
> > >
> > > Thanks again!
> > >
> > > On 5 June 2015 at 00:39, Alberto Rodriguez <ar...@gmail.com> wrote:
> > >
> > > > Hi Niklas,
> > > >
> > > > Thank you for replying, see attached the full crash.
> > > >
> > > > Kind regards,
> > > >
> > > > 2015-06-03 19:36 GMT+02:00 Niklas Nielsen <ni...@mesosphere.io>:
> > > >
> > > >> Hi Alberto,
> > > >>
> > > >> Can you share the full crash report with us?
> > > >>
> > > >> Niklas
> > > >>
> > > >> On 2 June 2015 at 02:37, Alberto Rodriguez <ar...@gmail.com>
> wrote:
> > > >>
> > > >> > Hi all,
> > > >> >
> > > >> > I've got a bunch of tests that are checking whether my spark
> process
> > > is
> > > >> > able to connect to a mesos cluster. The "happy path" (mesos up &
> > > >> running)
> > > >> > is working fine the problem comes when I'm testing a connection
> > with a
> > > >> > wrong mesos ip then I'm getting the following error:
> > > >> >
> > > >> > WARNING: Logging before InitGoogleLogging() is written to STDERR
> > > >> > W0602 11:26:03.549504 13269 sched.cpp:1323]
> > > >> > **************************************************
> > > >> > Scheduler driver bound to loopback interface! Cannot communicate
> > with
> > > >> > remote master(s). You might want to set 'LIBPROCESS_IP'
> environment
> > > >> > variable to use a routable IP address.
> > > >> > **************************************************
> > > >> > #
> > > >> > # A fatal error has been detected by the Java Runtime Environment:
> > > >> > #
> > > >> > # SIGSEGV (0xb) at pc=0x00007fcdf32c5660, pid=13125,
> > > >> tid=140517706200832
> > > >> > #
> > > >> > # JRE version: Java(TM) SE Runtime Environment (7.0_75-b13) (build
> > > >> > 1.7.0_75-b13)
> > > >> > # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.75-b04 mixed mode
> > > >> > linux-amd64 compressed oops)
> > > >> > # Problematic frame:
> > > >> > # C [libc.so.6+0x83660] cfree+0x220
> > > >> > #
> > > >> > # Core dump written. Default location:
> > > >> > /home/arodriguez/dev/datavis-master/back/core or core.13125 (max
> > size
> > > >> 50000
> > > >> > kB). To ensure a full core dump, try "ulimit -c unlimited" before
> > > >> starting
> > > >> > Java again
> > > >> > #
> > > >> > # An error report file with more information is saved as:
> > > >> > # /home/arodriguez/dev/datavis-master/back/hs_err_pid13125.log
> > > >> > #
> > > >> > # If you would like to submit a bug report, please visit:
> > > >> > # http://bugreport.sun.com/bugreport/crash.jsp
> > > >> > # The crash happened outside the Java Virtual Machine in native
> > code.
> > > >> > # See problematic frame for where to report the bug.
> > > >> > #
> > > >> > /bin/sh: línea 1: 13125 Abortado (`core' generado)
> > > >> > /usr/java/jdk1.7.0_75/jre/bin/java
> > > >> >
> > > >> >
> > > >>
> > >
> >
> -javaagent:/home/arodriguez/.m2/repository/org/jacoco/org.jacoco.agent/0.7.2.201409121644/org.jacoco.agent-0.$.2.201409121644-runtime.jar=destfile=/home/arodriguez/dev/datavis-master/back/target/jacocoIT.exec
> > > >> > -Xmx1024m -XX:MaxPermSize=256m
> > > >> > -Dlogback.configurationFile=conf/logger/develop.logger.xml
> > > >> > -Djava.security.polic$=conf/java.policy
> > > -XX:+HeapDumpOnOutOfMemoryError
> > > >> > org.apache.maven.surefire.booter.ForkedBooter
> > > >> >
> > > >> >
> > > >>
> > >
> >
> /home/arodriguez/dev/datavis-master/back/target/surefire/surefire6809257750333050101tmp
> > > >> >
> > > >> >
> > > >>
> > >
> >
> /home/arodriguez/dev/datav$s-master/back/target/surefire/surefire_02320528722071658975tmp
> > > >> >
> > > >> >
> > > >> > Any ideas?
> > > >> >
> > > >>
> > > >
> > > >
> > >
> >
>
Re: Native code error
Posted by Alex Rukletsov <al...@mesosphere.com>.
Mark it as a duplicate.
On 10 Jun 2015 8:21 am, "Alberto Rodriguez" <ar...@gmail.com> wrote:
> Thank you for replying and for opening a ticket. I also added a ticket
> related to the issue: https://issues.apache.org/jira/browse/MESOS-2820
> Should I close it?
>
> Thank you
>
> 2015-06-10 0:29 GMT+02:00 Niklas Nielsen <ni...@mesosphere.io>:
>
> > Thanks Alberto - I finally got to look at the trace and added a ticket to
> > track it: https://issues.apache.org/jira/browse/MESOS-2839
> >
> > Thanks again!
> >
> > On 5 June 2015 at 00:39, Alberto Rodriguez <ar...@gmail.com> wrote:
> >
> > > Hi Niklas,
> > >
> > > Thank you for replying, see attached the full crash.
> > >
> > > Kind regards,
> > >
> > > 2015-06-03 19:36 GMT+02:00 Niklas Nielsen <ni...@mesosphere.io>:
> > >
> > >> Hi Alberto,
> > >>
> > >> Can you share the full crash report with us?
> > >>
> > >> Niklas
> > >>
> > >> On 2 June 2015 at 02:37, Alberto Rodriguez <ar...@gmail.com> wrote:
> > >>
> > >> > Hi all,
> > >> >
> > >> > I've got a bunch of tests that are checking whether my spark process
> > is
> > >> > able to connect to a mesos cluster. The "happy path" (mesos up &
> > >> running)
> > >> > is working fine the problem comes when I'm testing a connection
> with a
> > >> > wrong mesos ip then I'm getting the following error:
> > >> >
> > >> > WARNING: Logging before InitGoogleLogging() is written to STDERR
> > >> > W0602 11:26:03.549504 13269 sched.cpp:1323]
> > >> > **************************************************
> > >> > Scheduler driver bound to loopback interface! Cannot communicate
> with
> > >> > remote master(s). You might want to set 'LIBPROCESS_IP' environment
> > >> > variable to use a routable IP address.
> > >> > **************************************************
> > >> > #
> > >> > # A fatal error has been detected by the Java Runtime Environment:
> > >> > #
> > >> > # SIGSEGV (0xb) at pc=0x00007fcdf32c5660, pid=13125,
> > >> tid=140517706200832
> > >> > #
> > >> > # JRE version: Java(TM) SE Runtime Environment (7.0_75-b13) (build
> > >> > 1.7.0_75-b13)
> > >> > # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.75-b04 mixed mode
> > >> > linux-amd64 compressed oops)
> > >> > # Problematic frame:
> > >> > # C [libc.so.6+0x83660] cfree+0x220
> > >> > #
> > >> > # Core dump written. Default location:
> > >> > /home/arodriguez/dev/datavis-master/back/core or core.13125 (max
> size
> > >> 50000
> > >> > kB). To ensure a full core dump, try "ulimit -c unlimited" before
> > >> starting
> > >> > Java again
> > >> > #
> > >> > # An error report file with more information is saved as:
> > >> > # /home/arodriguez/dev/datavis-master/back/hs_err_pid13125.log
> > >> > #
> > >> > # If you would like to submit a bug report, please visit:
> > >> > # http://bugreport.sun.com/bugreport/crash.jsp
> > >> > # The crash happened outside the Java Virtual Machine in native
> code.
> > >> > # See problematic frame for where to report the bug.
> > >> > #
> > >> > /bin/sh: línea 1: 13125 Abortado (`core' generado)
> > >> > /usr/java/jdk1.7.0_75/jre/bin/java
> > >> >
> > >> >
> > >>
> >
> -javaagent:/home/arodriguez/.m2/repository/org/jacoco/org.jacoco.agent/0.7.2.201409121644/org.jacoco.agent-0.$.2.201409121644-runtime.jar=destfile=/home/arodriguez/dev/datavis-master/back/target/jacocoIT.exec
> > >> > -Xmx1024m -XX:MaxPermSize=256m
> > >> > -Dlogback.configurationFile=conf/logger/develop.logger.xml
> > >> > -Djava.security.polic$=conf/java.policy
> > -XX:+HeapDumpOnOutOfMemoryError
> > >> > org.apache.maven.surefire.booter.ForkedBooter
> > >> >
> > >> >
> > >>
> >
> /home/arodriguez/dev/datavis-master/back/target/surefire/surefire6809257750333050101tmp
> > >> >
> > >> >
> > >>
> >
> /home/arodriguez/dev/datav$s-master/back/target/surefire/surefire_02320528722071658975tmp
> > >> >
> > >> >
> > >> > Any ideas?
> > >> >
> > >>
> > >
> > >
> >
>
Re: Native code error
Posted by Alberto Rodriguez <ar...@gmail.com>.
Thank you for replying and for opening a ticket. I also added a ticket
related to the issue: https://issues.apache.org/jira/browse/MESOS-2820
Should I close it?
Thank you
2015-06-10 0:29 GMT+02:00 Niklas Nielsen <ni...@mesosphere.io>:
> Thanks Alberto - I finally got to look at the trace and added a ticket to
> track it: https://issues.apache.org/jira/browse/MESOS-2839
>
> Thanks again!
>
> On 5 June 2015 at 00:39, Alberto Rodriguez <ar...@gmail.com> wrote:
>
> > Hi Niklas,
> >
> > Thank you for replying, see attached the full crash.
> >
> > Kind regards,
> >
> > 2015-06-03 19:36 GMT+02:00 Niklas Nielsen <ni...@mesosphere.io>:
> >
> >> Hi Alberto,
> >>
> >> Can you share the full crash report with us?
> >>
> >> Niklas
> >>
> >> On 2 June 2015 at 02:37, Alberto Rodriguez <ar...@gmail.com> wrote:
> >>
> >> > Hi all,
> >> >
> >> > I've got a bunch of tests that are checking whether my spark process
> is
> >> > able to connect to a mesos cluster. The "happy path" (mesos up &
> >> running)
> >> > is working fine the problem comes when I'm testing a connection with a
> >> > wrong mesos ip then I'm getting the following error:
> >> >
> >> > WARNING: Logging before InitGoogleLogging() is written to STDERR
> >> > W0602 11:26:03.549504 13269 sched.cpp:1323]
> >> > **************************************************
> >> > Scheduler driver bound to loopback interface! Cannot communicate with
> >> > remote master(s). You might want to set 'LIBPROCESS_IP' environment
> >> > variable to use a routable IP address.
> >> > **************************************************
> >> > #
> >> > # A fatal error has been detected by the Java Runtime Environment:
> >> > #
> >> > # SIGSEGV (0xb) at pc=0x00007fcdf32c5660, pid=13125,
> >> tid=140517706200832
> >> > #
> >> > # JRE version: Java(TM) SE Runtime Environment (7.0_75-b13) (build
> >> > 1.7.0_75-b13)
> >> > # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.75-b04 mixed mode
> >> > linux-amd64 compressed oops)
> >> > # Problematic frame:
> >> > # C [libc.so.6+0x83660] cfree+0x220
> >> > #
> >> > # Core dump written. Default location:
> >> > /home/arodriguez/dev/datavis-master/back/core or core.13125 (max size
> >> 50000
> >> > kB). To ensure a full core dump, try "ulimit -c unlimited" before
> >> starting
> >> > Java again
> >> > #
> >> > # An error report file with more information is saved as:
> >> > # /home/arodriguez/dev/datavis-master/back/hs_err_pid13125.log
> >> > #
> >> > # If you would like to submit a bug report, please visit:
> >> > # http://bugreport.sun.com/bugreport/crash.jsp
> >> > # The crash happened outside the Java Virtual Machine in native code.
> >> > # See problematic frame for where to report the bug.
> >> > #
> >> > /bin/sh: línea 1: 13125 Abortado (`core' generado)
> >> > /usr/java/jdk1.7.0_75/jre/bin/java
> >> >
> >> >
> >>
> -javaagent:/home/arodriguez/.m2/repository/org/jacoco/org.jacoco.agent/0.7.2.201409121644/org.jacoco.agent-0.$.2.201409121644-runtime.jar=destfile=/home/arodriguez/dev/datavis-master/back/target/jacocoIT.exec
> >> > -Xmx1024m -XX:MaxPermSize=256m
> >> > -Dlogback.configurationFile=conf/logger/develop.logger.xml
> >> > -Djava.security.polic$=conf/java.policy
> -XX:+HeapDumpOnOutOfMemoryError
> >> > org.apache.maven.surefire.booter.ForkedBooter
> >> >
> >> >
> >>
> /home/arodriguez/dev/datavis-master/back/target/surefire/surefire6809257750333050101tmp
> >> >
> >> >
> >>
> /home/arodriguez/dev/datav$s-master/back/target/surefire/surefire_02320528722071658975tmp
> >> >
> >> >
> >> > Any ideas?
> >> >
> >>
> >
> >
>
Re: Native code error
Posted by Niklas Nielsen <ni...@mesosphere.io>.
Thanks Alberto - I finally got to look at the trace and added a ticket to
track it: https://issues.apache.org/jira/browse/MESOS-2839
Thanks again!
On 5 June 2015 at 00:39, Alberto Rodriguez <ar...@gmail.com> wrote:
> Hi Niklas,
>
> Thank you for replying, see attached the full crash.
>
> Kind regards,
>
> 2015-06-03 19:36 GMT+02:00 Niklas Nielsen <ni...@mesosphere.io>:
>
>> Hi Alberto,
>>
>> Can you share the full crash report with us?
>>
>> Niklas
>>
>> On 2 June 2015 at 02:37, Alberto Rodriguez <ar...@gmail.com> wrote:
>>
>> > Hi all,
>> >
>> > I've got a bunch of tests that are checking whether my spark process is
>> > able to connect to a mesos cluster. The "happy path" (mesos up &
>> running)
>> > is working fine the problem comes when I'm testing a connection with a
>> > wrong mesos ip then I'm getting the following error:
>> >
>> > WARNING: Logging before InitGoogleLogging() is written to STDERR
>> > W0602 11:26:03.549504 13269 sched.cpp:1323]
>> > **************************************************
>> > Scheduler driver bound to loopback interface! Cannot communicate with
>> > remote master(s). You might want to set 'LIBPROCESS_IP' environment
>> > variable to use a routable IP address.
>> > **************************************************
>> > #
>> > # A fatal error has been detected by the Java Runtime Environment:
>> > #
>> > # SIGSEGV (0xb) at pc=0x00007fcdf32c5660, pid=13125,
>> tid=140517706200832
>> > #
>> > # JRE version: Java(TM) SE Runtime Environment (7.0_75-b13) (build
>> > 1.7.0_75-b13)
>> > # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.75-b04 mixed mode
>> > linux-amd64 compressed oops)
>> > # Problematic frame:
>> > # C [libc.so.6+0x83660] cfree+0x220
>> > #
>> > # Core dump written. Default location:
>> > /home/arodriguez/dev/datavis-master/back/core or core.13125 (max size
>> 50000
>> > kB). To ensure a full core dump, try "ulimit -c unlimited" before
>> starting
>> > Java again
>> > #
>> > # An error report file with more information is saved as:
>> > # /home/arodriguez/dev/datavis-master/back/hs_err_pid13125.log
>> > #
>> > # If you would like to submit a bug report, please visit:
>> > # http://bugreport.sun.com/bugreport/crash.jsp
>> > # The crash happened outside the Java Virtual Machine in native code.
>> > # See problematic frame for where to report the bug.
>> > #
>> > /bin/sh: línea 1: 13125 Abortado (`core' generado)
>> > /usr/java/jdk1.7.0_75/jre/bin/java
>> >
>> >
>> -javaagent:/home/arodriguez/.m2/repository/org/jacoco/org.jacoco.agent/0.7.2.201409121644/org.jacoco.agent-0.$.2.201409121644-runtime.jar=destfile=/home/arodriguez/dev/datavis-master/back/target/jacocoIT.exec
>> > -Xmx1024m -XX:MaxPermSize=256m
>> > -Dlogback.configurationFile=conf/logger/develop.logger.xml
>> > -Djava.security.polic$=conf/java.policy -XX:+HeapDumpOnOutOfMemoryError
>> > org.apache.maven.surefire.booter.ForkedBooter
>> >
>> >
>> /home/arodriguez/dev/datavis-master/back/target/surefire/surefire6809257750333050101tmp
>> >
>> >
>> /home/arodriguez/dev/datav$s-master/back/target/surefire/surefire_02320528722071658975tmp
>> >
>> >
>> > Any ideas?
>> >
>>
>
>
Re: Native code error
Posted by Alberto Rodriguez <ar...@gmail.com>.
Hi Niklas,
Thank you for replying, see attached the full crash.
Kind regards,
2015-06-03 19:36 GMT+02:00 Niklas Nielsen <ni...@mesosphere.io>:
> Hi Alberto,
>
> Can you share the full crash report with us?
>
> Niklas
>
> On 2 June 2015 at 02:37, Alberto Rodriguez <ar...@gmail.com> wrote:
>
> > Hi all,
> >
> > I've got a bunch of tests that are checking whether my spark process is
> > able to connect to a mesos cluster. The "happy path" (mesos up & running)
> > is working fine the problem comes when I'm testing a connection with a
> > wrong mesos ip then I'm getting the following error:
> >
> > WARNING: Logging before InitGoogleLogging() is written to STDERR
> > W0602 11:26:03.549504 13269 sched.cpp:1323]
> > **************************************************
> > Scheduler driver bound to loopback interface! Cannot communicate with
> > remote master(s). You might want to set 'LIBPROCESS_IP' environment
> > variable to use a routable IP address.
> > **************************************************
> > #
> > # A fatal error has been detected by the Java Runtime Environment:
> > #
> > # SIGSEGV (0xb) at pc=0x00007fcdf32c5660, pid=13125, tid=140517706200832
> > #
> > # JRE version: Java(TM) SE Runtime Environment (7.0_75-b13) (build
> > 1.7.0_75-b13)
> > # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.75-b04 mixed mode
> > linux-amd64 compressed oops)
> > # Problematic frame:
> > # C [libc.so.6+0x83660] cfree+0x220
> > #
> > # Core dump written. Default location:
> > /home/arodriguez/dev/datavis-master/back/core or core.13125 (max size
> 50000
> > kB). To ensure a full core dump, try "ulimit -c unlimited" before
> starting
> > Java again
> > #
> > # An error report file with more information is saved as:
> > # /home/arodriguez/dev/datavis-master/back/hs_err_pid13125.log
> > #
> > # If you would like to submit a bug report, please visit:
> > # http://bugreport.sun.com/bugreport/crash.jsp
> > # The crash happened outside the Java Virtual Machine in native code.
> > # See problematic frame for where to report the bug.
> > #
> > /bin/sh: línea 1: 13125 Abortado (`core' generado)
> > /usr/java/jdk1.7.0_75/jre/bin/java
> >
> >
> -javaagent:/home/arodriguez/.m2/repository/org/jacoco/org.jacoco.agent/0.7.2.201409121644/org.jacoco.agent-0.$.2.201409121644-runtime.jar=destfile=/home/arodriguez/dev/datavis-master/back/target/jacocoIT.exec
> > -Xmx1024m -XX:MaxPermSize=256m
> > -Dlogback.configurationFile=conf/logger/develop.logger.xml
> > -Djava.security.polic$=conf/java.policy -XX:+HeapDumpOnOutOfMemoryError
> > org.apache.maven.surefire.booter.ForkedBooter
> >
> >
> /home/arodriguez/dev/datavis-master/back/target/surefire/surefire6809257750333050101tmp
> >
> >
> /home/arodriguez/dev/datav$s-master/back/target/surefire/surefire_02320528722071658975tmp
> >
> >
> > Any ideas?
> >
>
Re: Native code error
Posted by Niklas Nielsen <ni...@mesosphere.io>.
Hi Alberto,
Can you share the full crash report with us?
Niklas
On 2 June 2015 at 02:37, Alberto Rodriguez <ar...@gmail.com> wrote:
> Hi all,
>
> I've got a bunch of tests that are checking whether my spark process is
> able to connect to a mesos cluster. The "happy path" (mesos up & running)
> is working fine the problem comes when I'm testing a connection with a
> wrong mesos ip then I'm getting the following error:
>
> WARNING: Logging before InitGoogleLogging() is written to STDERR
> W0602 11:26:03.549504 13269 sched.cpp:1323]
> **************************************************
> Scheduler driver bound to loopback interface! Cannot communicate with
> remote master(s). You might want to set 'LIBPROCESS_IP' environment
> variable to use a routable IP address.
> **************************************************
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x00007fcdf32c5660, pid=13125, tid=140517706200832
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_75-b13) (build
> 1.7.0_75-b13)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.75-b04 mixed mode
> linux-amd64 compressed oops)
> # Problematic frame:
> # C [libc.so.6+0x83660] cfree+0x220
> #
> # Core dump written. Default location:
> /home/arodriguez/dev/datavis-master/back/core or core.13125 (max size 50000
> kB). To ensure a full core dump, try "ulimit -c unlimited" before starting
> Java again
> #
> # An error report file with more information is saved as:
> # /home/arodriguez/dev/datavis-master/back/hs_err_pid13125.log
> #
> # If you would like to submit a bug report, please visit:
> # http://bugreport.sun.com/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #
> /bin/sh: línea 1: 13125 Abortado (`core' generado)
> /usr/java/jdk1.7.0_75/jre/bin/java
>
> -javaagent:/home/arodriguez/.m2/repository/org/jacoco/org.jacoco.agent/0.7.2.201409121644/org.jacoco.agent-0.$.2.201409121644-runtime.jar=destfile=/home/arodriguez/dev/datavis-master/back/target/jacocoIT.exec
> -Xmx1024m -XX:MaxPermSize=256m
> -Dlogback.configurationFile=conf/logger/develop.logger.xml
> -Djava.security.polic$=conf/java.policy -XX:+HeapDumpOnOutOfMemoryError
> org.apache.maven.surefire.booter.ForkedBooter
>
> /home/arodriguez/dev/datavis-master/back/target/surefire/surefire6809257750333050101tmp
>
> /home/arodriguez/dev/datav$s-master/back/target/surefire/surefire_02320528722071658975tmp
>
>
> Any ideas?
>