Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems with JRE #23

Open
JoschaMiddendorf opened this issue Oct 17, 2018 · 4 comments
Open

Problems with JRE #23

JoschaMiddendorf opened this issue Oct 17, 2018 · 4 comments

Comments

@JoschaMiddendorf
Copy link

JoschaMiddendorf commented Oct 17, 2018

After updating UnRaid, im getting the following output in my log on every try trigering the script. Do someone has a clue what's that about?

---------------------------------- README-----------------------------------

Use excludes: /config/amc-exclude-list.txt (1)

A fatal error has been detected by the Java Runtime Environment:

SIGSEGV (0xb) at pc=0x0000154f72d43a72, pid=146, tid=0x0000154fee607700

JRE version: Java(TM) SE Runtime Environment (8.0_161-b12) (build 1.8.0_161-b12)

Java VM: Java HotSpot(TM) 64-Bit Server VM (25.161-b12 mixed mode linux-amd64 compressed oops)
Problematic frame:
C [libmediainfo.so.0+0x3c3a72]

Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again

An error report file with more information is saved as:

/tmp/hs_err_pid146.log

If you would like to submit a bug report, please visit:
http://bugreport.java.com/bugreport/crash.jsp
The crash happened outside the Java Virtual Machine in native code.
See problematic frame for where to report the bug.

Aborted

@JoschaMiddendorf
Copy link
Author

Simply reinstalling it completely solved the issue for me. No changes on my config. Stil don't know where the issue came from but now it works again.

@JoschaMiddendorf
Copy link
Author

The problem occurred again and wasn't resolvable by reinstallation.

@trinsic
Copy link

trinsic commented Mar 30, 2019

Getting the same error message.

@austin-millan
Copy link

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants