[Mesa-users] Segmantation fault problem in DRI

김명진(Myungjin Kim) 선임연구원 두산로보틱스 myungjin.kim at doosan.com
Wed Jan 9 13:13:03 UTC 2019


Hello,

I’m currently developing a JavaFX based UI software on linux system.
But, my application is terminated with a segmentation fault after 1 or 2 days running.
I found out where a segmentation fault occurred from the error report written by the Java Virtual Machine(JVM).
A segmentation fault occurrence location always seems to be the same and it is in the i965_dri.so module.
You can see the first part of the error report in below.
I don’t know how can I solve this problem. So, please give me any advice about this problem.
If you need, then I can support additional log data.

Thank you.

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x4b07ec5e, pid=657, tid=0x4ea55b40
#
# JRE version: Java(TM) SE Runtime Environment (8.0_152-b16) (build 1.8.0_152-b16)
# Java VM: Java HotSpot(TM) Server VM (25.152-b16 mixed mode linux-x86 )
# Problematic frame:
# C  [i965_dri.so+0x40ac5e]
#
# Core dump written. Default location: /home/dra/Application/20181214/DRSC/core or core.657
#
# 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 (0x4d84d000):  JavaThread "QuantumRenderer-0" daemon [_thread_in_native, id=846, stack(0x4ea05000,0x4ea56000)]

siginfo: si_signo: 11 (SIGSEGV), si_code: 1 (SEGV_MAPERR), si_addr: 0x00000180

Registers:
EAX=0x00000000, EBX=0x4b588000, ECX=0x00000000, EDX=0x00000000
ESP=0x4ea549d0, EBP=0x00000001, ESI=0xbf9f99d0, EDI=0x00000000
EIP=0x4b07ec5e, EFLAGS=0x00010202, CR2=0x00000180

Top of Stack: (sp=0x4ea549d0)
0x4ea549d0:   4a955198 4b588000 4ea54a18 00000000
0x4ea549e0:   42800000 00000000 4b07ec49 4b588000
0x4ea549f0:   bf9f99d0 4a955198 00000000 4b06fd4f
0x4ea54a00:   4a955198 00000000 00000000 00000001
0x4ea54a10:   00000000 00000000 00000000 4b07474a
0x4ea54a20:   00000000 3f2aaaab 00000000 00000000
0x4ea54a30:   3eaaaaab 00000000 00000000 00000000
0x4ea54a40:   00000000 3f2aaaab 4b0770f9 960b5400

Instructions: (pc=0x4b07ec5e)
0x4b07ec3e:   00 00 55 57 56 53 e8 67 61 c2 ff 81 c3 b7 93 50
0x4b07ec4e:   00 83 ec 1c 8b 7c 24 34 8b 54 24 38 8b 6c 24 3c
0x4b07ec5e:   8b b7 80 01 00 00 83 fe 03 74 1f 83 fe 04 74 3a
0x4b07ec6e:   83 fe 02 b8 00 00 00 00 0f 45 f0 83 c4 1c 89 f0

Register to memory mapping:

EAX=0x00000000 is an unknown value
EBX=0x4b588000: <offset 0x914000> in /usr/lib/i386-linux-gnu/dri/i965_dri.so at 0x4ac74000
ECX=0x00000000 is an unknown value
EDX=0x00000000 is an unknown value
ESP=0x4ea549d0 is pointing into the stack for thread: 0x4d84d000
EBP=0x00000001 is an unknown value
ESI=0xbf9f99d0 is an unknown value
EDI=0x00000000 is an unknown value


Stack: [0x4ea05000,0x4ea56000],  sp=0x4ea549d0,  free space=318k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  [i965_dri.so+0x40ac5e]

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
J 7607  com.sun.prism.es2.GLContext.nDrawIndexedQuads(JI[F[B)V (0 bytes) @ 0xa84bb099 [0xa84bb020+0x79]
J 13062 C2 com.sun.prism.es2.ES2SwapChain.prepare(Lcom/sun/javafx/geom/Rectangle;)Z (184 bytes) @ 0xa7ea1da0 [0xa7ea18a0+0x500]
J 16206 C2 com.sun.javafx.tk.quantum.PresentingPainter.run()V (675 bytes) @ 0xa8b17034 [0xa8b16980+0x6b4]
J 13591 C2 com.sun.javafx.tk.RenderJob.run()V (105 bytes) @ 0xa899d420 [0xa899d320+0x100]
J 13740% C2 java.util.concurrent.ThreadPoolExecutor.runWorker(Ljava/util/concurrent/ThreadPoolExecutor$Worker;)V (225 bytes) @ 0xa9013e34 [0xa9013d00+0x134]
j  java.util.concurrent.ThreadPoolExecutor$Worker.run()V+5
j  com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run()V+8
j  java.lang.Thread.run()V+11
v  ~StubRoutines::call_stub
…

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-users/attachments/20190109/bdc0b522/attachment.html>


More information about the mesa-users mailing list