Java crash on Ubuntu linux
up vote
0
down vote
favorite
Suddenly from one day to the next, with no apparent software or configuration changes we are starting to get JVM crashes with the following in the syslog:
*** Error in `java': double free or corruption (fasttop): 0x00007f70344753d0 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7f7051ca17e5]
/lib/x86_64-linux-gnu/libc.so.6(+0x8037a)[0x7f7051caa37a]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x4c)[0x7f7051cae53c]
/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/libfontmanager.so(Java_sun_font_FreetypeFontScaler_disposeNativeScaler+0x64)[0x7f7028cd6154]
[0x7f7039017e07]
As far as I can gather from similar issues this is caused by an error in a native library - in this case probably libfontmanager.so.
How can this be diagnosed further? Can I get a java-stacktrace of the situation causing this problem? In case this is a concurrency issue, it could perhaps be fixed on the java-side of things.
Using OpenJDK 1.8.0_181 on Ubuntu 16.04.5. I am unable to find a newer java build in Ubuntu repositories - maybe I overlooked it?
This is a production environment, so upgrade of major java version etc. would not be easy.
java linux ubuntu jvm jni
asked Nov 7 at 10:24
Dennis Thrysøe
58131027
|
show 2 more comments
up vote
0
down vote
favorite
Suddenly from one day to the next, with no apparent software or configuration changes we are starting to get JVM crashes with the following in the syslog:
*** Error in `java': double free or corruption (fasttop): 0x00007f70344753d0 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7f7051ca17e5]
/lib/x86_64-linux-gnu/libc.so.6(+0x8037a)[0x7f7051caa37a]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x4c)[0x7f7051cae53c]
/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/libfontmanager.so(Java_sun_font_FreetypeFontScaler_disposeNativeScaler+0x64)[0x7f7028cd6154]
[0x7f7039017e07]
As far as I can gather from similar issues this is caused by an error in a native library - in this case probably libfontmanager.so.
How can this be diagnosed further? Can I get a java-stacktrace of the situation causing this problem? In case this is a concurrency issue, it could perhaps be fixed on the java-side of things.
Using OpenJDK 1.8.0_181 on Ubuntu 16.04.5. I am unable to find a newer java build in Ubuntu repositories - maybe I overlooked it?
This is a production environment, so upgrade of major java version etc. would not be easy.
java linux ubuntu jvm jni
asked Nov 7 at 10:24
Dennis Thrysøe
58131027
Are you using JNI in your app?
– user10527814
Nov 7 at 10:31
Also, are you using any kind of logging to file in your app?
– Blagoj Atanasovski
Nov 7 at 10:36
No JNI is used in the application, but plenty of file logging.
– Dennis Thrysøe
Nov 7 at 12:08
This looks like a JDK bug. OpenJDK 1.8.0_181 appears to be the latest available at packages.ubuntu.com/hu/source/xenial/openjdk-8 Can you post a full stack trace?
– Andrew Henle
Nov 7 at 14:33
The above is the full backtrace. I wish I knew how to get a stacktrace of this fault/situation.
– Dennis Thrysøe
Nov 7 at 14:34
|
show 2 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Suddenly from one day to the next, with no apparent software or configuration changes we are starting to get JVM crashes with the following in the syslog:
*** Error in `java': double free or corruption (fasttop): 0x00007f70344753d0 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7f7051ca17e5]
/lib/x86_64-linux-gnu/libc.so.6(+0x8037a)[0x7f7051caa37a]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x4c)[0x7f7051cae53c]
/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/libfontmanager.so(Java_sun_font_FreetypeFontScaler_disposeNativeScaler+0x64)[0x7f7028cd6154]
[0x7f7039017e07]
As far as I can gather from similar issues this is caused by an error in a native library - in this case probably libfontmanager.so.
How can this be diagnosed further? Can I get a java-stacktrace of the situation causing this problem? In case this is a concurrency issue, it could perhaps be fixed on the java-side of things.
Using OpenJDK 1.8.0_181 on Ubuntu 16.04.5. I am unable to find a newer java build in Ubuntu repositories - maybe I overlooked it?
This is a production environment, so upgrade of major java version etc. would not be easy.
java linux ubuntu jvm jni
asked Nov 7 at 10:24
Dennis Thrysøe
58131027
Suddenly from one day to the next, with no apparent software or configuration changes we are starting to get JVM crashes with the following in the syslog:
*** Error in `java': double free or corruption (fasttop): 0x00007f70344753d0 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7f7051ca17e5]
/lib/x86_64-linux-gnu/libc.so.6(+0x8037a)[0x7f7051caa37a]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x4c)[0x7f7051cae53c]
/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/libfontmanager.so(Java_sun_font_FreetypeFontScaler_disposeNativeScaler+0x64)[0x7f7028cd6154]
[0x7f7039017e07]
As far as I can gather from similar issues this is caused by an error in a native library - in this case probably libfontmanager.so.
How can this be diagnosed further? Can I get a java-stacktrace of the situation causing this problem? In case this is a concurrency issue, it could perhaps be fixed on the java-side of things.
Using OpenJDK 1.8.0_181 on Ubuntu 16.04.5. I am unable to find a newer java build in Ubuntu repositories - maybe I overlooked it?
This is a production environment, so upgrade of major java version etc. would not be easy.
java linux ubuntu jvm jni
java linux ubuntu jvm jni
asked Nov 7 at 10:24
Dennis Thrysøe
58131027
asked Nov 7 at 10:24
Dennis Thrysøe
58131027
asked Nov 7 at 10:24
Dennis Thrysøe
58131027
asked Nov 7 at 10:24
Dennis Thrysøe
58131027
asked Nov 7 at 10:24
Dennis Thrysøe
58131027
58131027
Are you using JNI in your app?
– user10527814
Nov 7 at 10:31
Also, are you using any kind of logging to file in your app?
– Blagoj Atanasovski
Nov 7 at 10:36
No JNI is used in the application, but plenty of file logging.
– Dennis Thrysøe
Nov 7 at 12:08
This looks like a JDK bug. OpenJDK 1.8.0_181 appears to be the latest available at packages.ubuntu.com/hu/source/xenial/openjdk-8 Can you post a full stack trace?
– Andrew Henle
Nov 7 at 14:33
The above is the full backtrace. I wish I knew how to get a stacktrace of this fault/situation.
– Dennis Thrysøe
Nov 7 at 14:34
|
show 2 more comments
Are you using JNI in your app?
– user10527814
Nov 7 at 10:31
Also, are you using any kind of logging to file in your app?
– Blagoj Atanasovski
Nov 7 at 10:36
No JNI is used in the application, but plenty of file logging.
– Dennis Thrysøe
Nov 7 at 12:08
This looks like a JDK bug. OpenJDK 1.8.0_181 appears to be the latest available at packages.ubuntu.com/hu/source/xenial/openjdk-8 Can you post a full stack trace?
– Andrew Henle
Nov 7 at 14:33
The above is the full backtrace. I wish I knew how to get a stacktrace of this fault/situation.
– Dennis Thrysøe
Nov 7 at 14:34
Are you using JNI in your app?
– user10527814
Nov 7 at 10:31
Are you using JNI in your app?
– user10527814
Nov 7 at 10:31
Also, are you using any kind of logging to file in your app?
– Blagoj Atanasovski
Nov 7 at 10:36
Also, are you using any kind of logging to file in your app?
– Blagoj Atanasovski
Nov 7 at 10:36
No JNI is used in the application, but plenty of file logging.
– Dennis Thrysøe
Nov 7 at 12:08
No JNI is used in the application, but plenty of file logging.
– Dennis Thrysøe
Nov 7 at 12:08
This looks like a JDK bug. OpenJDK 1.8.0_181 appears to be the latest available at packages.ubuntu.com/hu/source/xenial/openjdk-8 Can you post a full stack trace?
– Andrew Henle
Nov 7 at 14:33
This looks like a JDK bug. OpenJDK 1.8.0_181 appears to be the latest available at packages.ubuntu.com/hu/source/xenial/openjdk-8 Can you post a full stack trace?
– Andrew Henle
Nov 7 at 14:33
The above is the full backtrace. I wish I knew how to get a stacktrace of this fault/situation.
– Dennis Thrysøe
Nov 7 at 14:34
The above is the full backtrace. I wish I knew how to get a stacktrace of this fault/situation.
– Dennis Thrysøe
Nov 7 at 14:34
|
show 2 more comments
1 Answer
1
active
oldest
votes
up vote
0
down vote
Looks like this was possibly caused by pdfbox version 1.8 (or actually possibly more likely fontbox version 1.8). After upgrading both to version 2.0, the problem looks like it might have gone away.
However several things were tried in a frenzy, to try to get rid of this problem, so this is not known for certain. Also the issue was intermittent, and might possibly not have been solved, even though it looks like it until now.
answered Nov 12 at 7:01
Dennis Thrysøe
58131027
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Looks like this was possibly caused by pdfbox version 1.8 (or actually possibly more likely fontbox version 1.8). After upgrading both to version 2.0, the problem looks like it might have gone away.
However several things were tried in a frenzy, to try to get rid of this problem, so this is not known for certain. Also the issue was intermittent, and might possibly not have been solved, even though it looks like it until now.
answered Nov 12 at 7:01
Dennis Thrysøe
58131027
add a comment |
up vote
0
down vote
Looks like this was possibly caused by pdfbox version 1.8 (or actually possibly more likely fontbox version 1.8). After upgrading both to version 2.0, the problem looks like it might have gone away.
However several things were tried in a frenzy, to try to get rid of this problem, so this is not known for certain. Also the issue was intermittent, and might possibly not have been solved, even though it looks like it until now.
answered Nov 12 at 7:01
Dennis Thrysøe
58131027
add a comment |
up vote
0
down vote
up vote
0
down vote
Looks like this was possibly caused by pdfbox version 1.8 (or actually possibly more likely fontbox version 1.8). After upgrading both to version 2.0, the problem looks like it might have gone away.
However several things were tried in a frenzy, to try to get rid of this problem, so this is not known for certain. Also the issue was intermittent, and might possibly not have been solved, even though it looks like it until now.
answered Nov 12 at 7:01
Dennis Thrysøe
58131027
Looks like this was possibly caused by pdfbox version 1.8 (or actually possibly more likely fontbox version 1.8). After upgrading both to version 2.0, the problem looks like it might have gone away.
However several things were tried in a frenzy, to try to get rid of this problem, so this is not known for certain. Also the issue was intermittent, and might possibly not have been solved, even though it looks like it until now.
answered Nov 12 at 7:01
Dennis Thrysøe
58131027
answered Nov 12 at 7:01
Dennis Thrysøe
58131027
answered Nov 12 at 7:01
Dennis Thrysøe
58131027
answered Nov 12 at 7:01
Dennis Thrysøe
58131027
58131027
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53187551%2fjava-crash-on-ubuntu-linux%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Are you using JNI in your app?
– user10527814
Nov 7 at 10:31
Also, are you using any kind of logging to file in your app?
– Blagoj Atanasovski
Nov 7 at 10:36
No JNI is used in the application, but plenty of file logging.
– Dennis Thrysøe
Nov 7 at 12:08
This looks like a JDK bug. OpenJDK 1.8.0_181 appears to be the latest available at packages.ubuntu.com/hu/source/xenial/openjdk-8 Can you post a full stack trace?
– Andrew Henle
Nov 7 at 14:33
The above is the full backtrace. I wish I knew how to get a stacktrace of this fault/situation.
– Dennis Thrysøe
Nov 7 at 14:34