#41
|
||||
|
||||
Thanks for the follow up. the board censors the word because it's part of a common curse word
__________________
JD-Dev & Server-Admin |
#42
|
|||
|
|||
Hello, in the last few days, I'd been noting JD2 keeps getting closed by itself but I don''t know why. It seems to be working rightly, downloads are finished and I don't see it crashing right while it is being active, but when I resume the system from a suspended state. In that condition, when I open it, it shows me the error message with red words (excerpt):
Code:
# # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000026c85fd8, pid=21720, tid=0x00000000000056fc # # JRE version: Java(TM) SE Runtime Environment (8.0_271-b09) (build 1.8.0_271-b09) # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.271-b09 mixed mode windows-amd64 compressed oops) # Problematic frame: # C 0x0000000026c85fd8 # # 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 (0x0000000021a69000): JavaThread "AWT-Windows" daemon [_thread_in_native, id=22268, stack(0x00000000223d0000,0x00000000224d0000)] siginfo: ExceptionCode=0xc0000005, ExceptionInformation=0x0000000000000008 0x0000000026c85fd8 Registers: RAX=0x0000000026284970, RBX=0x0000000000000000, RCX=0x00000000218f7300, RDX=0x00007ffea0d78cf0 RSP=0x00000000224ceb48, RBP=0x00000000224cec09, RSI=0x000000000000010d, RDI=0x0000000021a691f8 R8 =0x0000000000000000, R9 =0x0000000000000000, R10=0x00007ffea0d972d0, R11=0x0000000000000000 R12=0x0000000000000001, R13=0x000000000000a220, R14=0x00000000267e8830, R15=0x0000000000000111 RIP=0x0000000026c85fd8, EFLAGS=0x0000000000010206 Top of Stack: (sp=0x00000000224ceb48) 0x00000000224ceb48: 00007ffea0d204bb 0000000000000000 0x00000000224ceb58: 0000000000000000 0000000000000000 0x00000000224ceb68: 0000000002461472 00000000267e88d0 0x00000000224ceb78: 00007ffea0d1f46d 00000000267e88d0 (...) I leave you two logs: 27.10.20 19.55.44 <--> 27.10.20 19.55.49 jdlog://4498325302851/ Thanks. |
#43
|
||||
|
||||
Your java crashed in Graphic system, so something between java+os+graphic driver/card has caused the crash. Can be monitor standby/drive stuff/attach/detach of display.
__________________
JD-Dev & Server-Admin |
#44
|
|||
|
|||
I see, the issue has a sporadic behavior, but I will try to keep an eye on it and determine which could be causing it.
I will post here, provided I have any news about it. Thanks for your insights. |
#45
|
||||
|
||||
Thanks for trying to find a way to reproduce it Good luck Thumbs up!
__________________
JD-Dev & Server-Admin |
Thread Tools | |
Display Modes | |
|
|