...

The worst monsters in the Hearthlands warp the fabric of space and time...

...

Postby mvgulik » Wed Oct 21, 2020 1:55 am

...
Last edited by mvgulik on Fri Jul 04, 2025 7:54 am, edited 3 times in total.
mvgulik
 
Posts: 3751
Joined: Fri May 21, 2010 2:29 am

Re: Information about JVM crashes

Postby loftar » Wed Oct 21, 2020 2:06 am

mvgulik wrote:Are there any part of particular interest ... as direct posting some of those seems a bit awkward.

Those are some really huge crash logs. They aren't usually anywhere near that huge; I wonder if they've added some new information to the logs. Anyway, the most interesting part is the first part up until and including the (native) stackframe of the crashing thread.
"Object-oriented design is the roman numerals of computing." -- Rob Pike
User avatar
loftar
 
Posts: 9051
Joined: Fri Apr 03, 2009 7:05 am

...

Postby mvgulik » Wed Oct 21, 2020 2:27 am

...
Last edited by mvgulik on Fri Jul 04, 2025 7:54 am, edited 1 time in total.
mvgulik
 
Posts: 3751
Joined: Fri May 21, 2010 2:29 am

Re: Information about JVM crashes

Postby loftar » Wed Oct 21, 2020 4:21 pm

mvgulik wrote:Would that be the
Code: Select all
---------------  P R O C E S S  ---------------
Java Threads: ( => current thread )
part ? (ie: clipping "Other Threads:" section and below ?)

To cite the report above, it would be this part:
Code: Select all
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_STACK_OVERFLOW (0xc00000fd) at pc=0x5b601367, pid=3156, tid=0x00002b68
#
# JRE version: Java(TM) SE Runtime Environment (8.0_251-b08) (build 1.8.0_251-b08)
# Java VM: Java HotSpot(TM) Client VM (25.251-b08 mixed mode windows-x86 )
# Problematic frame:
# C [ig7icd32.dll+0x3f1367]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# 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.
#

--------------- T H R E A D ---------------

Current thread (0x45bcc000): JavaThread "AWT-EventQueue-0" [_thread_in_native, id=11112, stack(0x46a00000,0x46a50000)]

siginfo: ExceptionCode=0xc00000fd, ExceptionInformation=0x00000000 0x46a00000

Registers:
EAX=0x46a00000, EBX=0x46a4e5a0, ECX=0x469f27cc, EDX=0x00be0000
ESP=0x46a10ea8, EBP=0x46a10ebc, ESI=0x46a49bf8, EDI=0x4994a288
EIP=0x5b601367, EFLAGS=0x00010206

Top of Stack: (sp=0x46a10ea8)
0x46a10ea8: 4994a288 5b4b2642 46a2f5b8 5b65e63e
0x46a10eb8: ffffffff 46a2f5c4 5b4b2c97 00000077
0x46a10ec8: 46a2c378 46a2f564 4994a288 499a0ae8
0x46a10ed8: 00000000 00000000 00000000 00000000
0x46a10ee8: 00000000 00000000 00000000 00000000
0x46a10ef8: 00000000 00000000 00000000 00000000
0x46a10f08: 00000000 00000000 00000000 00000000
0x46a10f18: 00000000 00000000 00000000 00000000

Instructions: (pc=0x5b601367)
0x5b601347: 1b c0 f7 d0 23 c8 8b c4 25 00 f0 ff ff 3b c8 72
0x5b601357: 0a 8b c1 59 94 8b 00 89 04 24 c3 2d 00 10 00 00
0x5b601367: 85 00 eb e9 cc cc cc cc cc 55 8b ec 56 33 c0 50
0x5b601377: 50 50 50 50 50 50 50 8b 55 0c 8d 49 00 8a 02 0a


Register to memory mapping:

EAX=0x46a00000 is an unknown value
EBX=0x46a4e5a0 is pointing into the stack for thread: 0x45bcc000
ECX=0x469f27cc is an unknown value
EDX=0x00be0000 is an unknown value
ESP=0x46a10ea8 is pointing into the stack for thread: 0x45bcc000
EBP=0x46a10ebc is pointing into the stack for thread: 0x45bcc000
ESI=0x46a49bf8 is pointing into the stack for thread: 0x45bcc000
EDI=0x4994a288 is an unknown value


Stack: [0x46a00000,0x46a50000], sp=0x46a10ea8, free space=67k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [ig7icd32.dll+0x3f1367]
C [ig7icd32.dll+0x2a2c97]
C [ig7icd32.dll+0x2a5358]
C [ig7icd32.dll+0x38e6ac]
C [ig7icd32.dll+0x38ed2a]
C [ig7icd32.dll+0x120697]
C [ig7icd32.dll+0x38f76a]
C [ig7icd32.dll+0x120686]
C [ig7icd32.dll+0x38ea8f]
C [ig7icd32.dll+0x120697]
C [ig7icd32.dll+0x38c967]
C [ig7icd32.dll+0x38ec36]
C [ig7icd32.dll+0x120697]
C [ig7icd32.dll+0x38ed06]
C [ig7icd32.dll+0x120697]
C [ig7icd32.dll+0x38f3ec]
C [ig7icd32.dll+0x120697]
C [ig7icd32.dll+0x38f738]
C [ig7icd32.dll+0x120686]
C [ig7icd32.dll+0x38ea8f]
C [ig7icd32.dll+0x1207c5]
C [ig7icd32.dll+0x38f14d]
C [ig7icd32.dll+0x120697]
C [ig7icd32.dll+0x38ea8f]
C [ig7icd32.dll+0x120697]
C [ig7icd32.dll+0x34d805]
C [ig7icd32.dll+0x34d72a]
C [ig7icd32.dll+0x1a9cc7]
C [ig7icd32.dll+0x11daaf]
C [ig7icd32.dll+0x11ea2a]
C [ig7icd32.dll+0x11ebd2]
C [ig7icd32.dll+0x238592]
C [jogl_desktop.dll+0x2883f]
j jogamp.opengl.gl4.GL4bcImpl.dispatch_glLinkProgram1(IJ)V+0
j jogamp.opengl.gl4.GL4bcImpl.glLinkProgram(I)V+34
j haven.render.gl.GLProgram$ProgOb.create(Ljavax/media/opengl/GL3;)V+99
j haven.render.gl.BGL$2.run(Ljavax/media/opengl/GL3;)V+5
J 744 C1 haven.render.gl.BufferBGL.run(Ljavax/media/opengl/GL3;)V (47 bytes) @ 0x02c90a04 [0x02c909b0+0x54]
j haven.render.gl.GLEnvironment.process(Ljavax/media/opengl/GL3;)V+134
j haven.JOGLPanel.redraw(Ljavax/media/opengl/GL3;)V+95
j haven.JOGLPanel.access$000(Lhaven/JOGLPanel;Ljavax/media/opengl/GL3;)V+2
j haven.JOGLPanel$1.display(Ljavax/media/opengl/GLAutoDrawable;)V+15
j jogamp.opengl.GLDrawableHelper.displayImpl(Ljavax/media/opengl/GLAutoDrawable;)V+81
j jogamp.opengl.GLDrawableHelper.display(Ljavax/media/opengl/GLAutoDrawable;)V+2
j javax.media.opengl.awt.GLCanvas$9.run()V+118
j jogamp.opengl.GLDrawableHelper.invokeGLImpl(Ljavax/media/opengl/GLDrawable;Ljavax/media/opengl/GLContext;Ljava/lang/Runnable;Ljava/lang/Runnable;)V+206
j jogamp.opengl.GLDrawableHelper.invokeGL(Ljavax/media/opengl/GLDrawable;Ljavax/media/opengl/GLContext;Ljava/lang/Runnable;Ljava/lang/Runnable;)V+80
j javax.media.opengl.awt.GLCanvas$10.run()V+73
j java.awt.event.InvocationEvent.dispatch()V+11
j java.awt.EventQueue.dispatchEventImpl(Ljava/awt/AWTEvent;Ljava/lang/Object;)V+21
j java.awt.EventQueue.access$500(Ljava/awt/EventQueue;Ljava/awt/AWTEvent;Ljava/lang/Object;)V+3
j java.awt.EventQueue$3.run()Ljava/lang/Void;+32
j java.awt.EventQueue$3.run()Ljava/lang/Object;+1
v ~StubRoutines::call_stub
V [jvm.dll+0x15c725]
V [jvm.dll+0x228b6e]
V [jvm.dll+0x15c7be]
V [jvm.dll+0x10c45f]
C [java.dll+0x102f]
j java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Ljava/security/PrivilegedAction;Ljava/security/AccessControlContext;Ljava/security/AccessControlContext;)Ljava/lang/Object;+18
j java.awt.EventQueue.dispatchEvent(Ljava/awt/AWTEvent;)V+46
j java.awt.EventDispatchThread.pumpOneEventForFilters(I)V+140
j java.awt.EventDispatchThread.pumpEventsForFilter(ILjava/awt/Conditional;Ljava/awt/EventFilter;)V+35
j java.awt.EventDispatchThread.pumpEventsForHierarchy(ILjava/awt/Conditional;Ljava/awt/Component;)V+11
j java.awt.EventDispatchThread.pumpEvents(ILjava/awt/Conditional;)V+4
j java.awt.EventDispatchThread.pumpEvents(Ljava/awt/Conditional;)V+3
j java.awt.EventDispatchThread.run()V+9
v ~StubRoutines::call_stub
V [jvm.dll+0x15c725]
V [jvm.dll+0x228b6e]
V [jvm.dll+0x15c7be]
V [jvm.dll+0x15c946]
V [jvm.dll+0x15c9b7]
V [jvm.dll+0x1003df]
V [jvm.dll+0x17f940]
V [jvm.dll+0x1801ba]
V [jvm.dll+0x1c6ea6]
C [msvcr100.dll+0x5c556]
C [msvcr100.dll+0x5c600]
C [KERNEL32.DLL+0x20419]
C [ntdll.dll+0x666dd]
C [ntdll.dll+0x666ad]
C 0x00000000

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j jogamp.opengl.gl4.GL4bcImpl.dispatch_glLinkProgram1(IJ)V+0
j jogamp.opengl.gl4.GL4bcImpl.glLinkProgram(I)V+34
j haven.render.gl.GLProgram$ProgOb.create(Ljavax/media/opengl/GL3;)V+99
j haven.render.gl.BGL$2.run(Ljavax/media/opengl/GL3;)V+5
J 744 C1 haven.render.gl.BufferBGL.run(Ljavax/media/opengl/GL3;)V (47 bytes) @ 0x02c90a04 [0x02c909b0+0x54]
j haven.render.gl.GLEnvironment.process(Ljavax/media/opengl/GL3;)V+134
j haven.JOGLPanel.redraw(Ljavax/media/opengl/GL3;)V+95
j haven.JOGLPanel.access$000(Lhaven/JOGLPanel;Ljavax/media/opengl/GL3;)V+2
j haven.JOGLPanel$1.display(Ljavax/media/opengl/GLAutoDrawable;)V+15
j jogamp.opengl.GLDrawableHelper.displayImpl(Ljavax/media/opengl/GLAutoDrawable;)V+81
j jogamp.opengl.GLDrawableHelper.display(Ljavax/media/opengl/GLAutoDrawable;)V+2
j javax.media.opengl.awt.GLCanvas$9.run()V+118
j jogamp.opengl.GLDrawableHelper.invokeGLImpl(Ljavax/media/opengl/GLDrawable;Ljavax/media/opengl/GLContext;Ljava/lang/Runnable;Ljava/lang/Runnable;)V+206
j jogamp.opengl.GLDrawableHelper.invokeGL(Ljavax/media/opengl/GLDrawable;Ljavax/media/opengl/GLContext;Ljava/lang/Runnable;Ljava/lang/Runnable;)V+80
j javax.media.opengl.awt.GLCanvas$10.run()V+73
j java.awt.event.InvocationEvent.dispatch()V+11
j java.awt.EventQueue.dispatchEventImpl(Ljava/awt/AWTEvent;Ljava/lang/Object;)V+21
j java.awt.EventQueue.access$500(Ljava/awt/EventQueue;Ljava/awt/AWTEvent;Ljava/lang/Object;)V+3
j java.awt.EventQueue$3.run()Ljava/lang/Void;+32
j java.awt.EventQueue$3.run()Ljava/lang/Object;+1
v ~StubRoutines::call_stub
j java.security.AccessController.doPrivileged(Ljava/security/PrivilegedAction;Ljava/security/AccessControlContext;)Ljava/lang/Object;+0
j java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Ljava/security/PrivilegedAction;Ljava/security/AccessControlContext;Ljava/security/AccessControlContext;)Ljava/lang/Object;+18
j java.awt.EventQueue.dispatchEvent(Ljava/awt/AWTEvent;)V+46
j java.awt.EventDispatchThread.pumpOneEventForFilters(I)V+140
j java.awt.EventDispatchThread.pumpEventsForFilter(ILjava/awt/Conditional;Ljava/awt/EventFilter;)V+35
j java.awt.EventDispatchThread.pumpEventsForHierarchy(ILjava/awt/Conditional;Ljava/awt/Component;)V+11
j java.awt.EventDispatchThread.pumpEvents(ILjava/awt/Conditional;)V+4
j java.awt.EventDispatchThread.pumpEvents(Ljava/awt/Conditional;)V+3
j java.awt.EventDispatchThread.run()V+9
v ~StubRoutines::call_stub
"Object-oriented design is the roman numerals of computing." -- Rob Pike
User avatar
loftar
 
Posts: 9051
Joined: Fri Apr 03, 2009 7:05 am

...

Postby mvgulik » Wed Oct 21, 2020 5:38 pm

...
Last edited by mvgulik on Fri Jul 04, 2025 7:53 am, edited 1 time in total.
mvgulik
 
Posts: 3751
Joined: Fri May 21, 2010 2:29 am

Re: JVM crash in libc.so

Postby loftar » Wed Oct 21, 2020 6:04 pm

That looks an awful lot like an OpenGL driver bug, seeing how it crashes in libc via a call to the OpenGL driver, in a call that shouldn't even be able to touch any potentially invalid memory.

What hardware and drivers are you using?
"Object-oriented design is the roman numerals of computing." -- Rob Pike
User avatar
loftar
 
Posts: 9051
Joined: Fri Apr 03, 2009 7:05 am

...

Postby mvgulik » Wed Oct 21, 2020 6:48 pm

...
Last edited by mvgulik on Fri Jul 04, 2025 7:53 am, edited 1 time in total.
mvgulik
 
Posts: 3751
Joined: Fri May 21, 2010 2:29 am

Re: JVM crash in libc.so

Postby MagicManICT » Wed Oct 21, 2020 11:34 pm

mvgulik wrote:For the video is seems to use the default drivers that come with the OS. (ie: no proprietary drivers are in use)

Seems like that could be a problem itself. Generic driver is trying to access memory the graphics device memory controller isn't allowing or something along that as a possible issue. I'm not even close to a Linux geek (not even much of a Windows one anymore). (Additional thoughts--it is a bit of a universal problem no matter the OS as different hardware manufacturers, even between model numbers, let alone generations, can change the needs for memory allocation and patterning.)
Opinions expressed in this statement are the authors alone and in no way reflect on the game development values of the actual developers.
User avatar
MagicManICT
 
Posts: 18435
Joined: Tue Aug 17, 2010 1:47 am

Re: JVM crash in libc.so

Postby loftar » Wed Oct 21, 2020 11:45 pm

mvgulik wrote:For the video is seems to use the default drivers that come with the OS. (ie: no proprietary drivers are in use)

If I were you, I'd make sure to install the debug symbols for libc and see if that expands the stack trace down into the driver. Since you are using the open source drivers, you should be able to install the debug symbols for those as well when you see from the expanded stack trace what file they come from. One of the problems with the log-file right now is that it stops directly at the first frame, in libc, which is, in all likelihood, due to a lack of debug symbols.

Also, I know next to nothing about Mint, but the drivers likely come from the Mesa package (which is commonly split up among several distro packages by the distro maintainers), so I'd check to see if they're using the latest version. Or contrariwise, perhaps, if they're using a too new, experimental version.

MagicManICT wrote:Seems like that could be a problem itself. Generic driver is trying to access memory the graphics device memory controller isn't allowing or something along that as a possible issue. I'm not even close to a Linux geek (not even much of a Windows one anymore).

From my (admittedly somewhat limited) knowledge of the Linux GPU driver stack, there shouldn't be any room for any such issue.
"Object-oriented design is the roman numerals of computing." -- Rob Pike
User avatar
loftar
 
Posts: 9051
Joined: Fri Apr 03, 2009 7:05 am

...

Postby mvgulik » Thu Oct 22, 2020 7:39 am

...
Last edited by mvgulik on Fri Jul 04, 2025 7:53 am, edited 1 time in total.
mvgulik
 
Posts: 3751
Joined: Fri May 21, 2010 2:29 am

Next

Return to Bugs

Who is online

Users browsing this forum: Claude [Bot], Dotbot [Bot] and 68 guests