J 32ShellFolder2.getDisplayNameOf(JJI)Ljava/lang/String +0 Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) T H R E A D -Ĭurrent thread (0x45975c00): JavaThread "Swing-Shell" daemon # See problematic frame for where to report the bug. # The crash happened outside the Java Virtual Machine in native code. # If you would like to submit a bug report, please visit: Minidumps are not enabled by default on client versions of Windows # Java VM: Java HotSpot(TM) Client VM (25.131-b11 mixed mode windows-x86 ) # A fatal error has been detected by the Java Runtime Environment: In the program folder I do get this error log Im having the same issue ive dropped to 6.7.1 from 7.0.0-b2 thinking this would correct it but I am getting a similar error as above in the other forums when adding a new directory the UMS system closes. It's currently listed as a bug in the Java bugtracker, which is resolved in Java 8u141 and Java 9.0.6 whenever these become available for download. Downgrade the Java version to at most Java 8u121.The two remaining options should then be to either: Since Microsoft has decided that updates should be forced in Windows 10, I guess downgrading from the flawed version isn't an option. To avoid the bug, breaking one of these conditions should be sufficient. In addition to having an updated Windows 10 with an updated Java, a God mode folder must exist on the computer. From what I understand, only Java versions after 8u121 are affected. It seems that there's a number of conditions that need to be met for the bug to manifest itself. It's a bug introduced by a recent Windows update (Windows 10 Creators Update v1703). This is a bug that has nothing to do with UMS but affects any Java program that opens the "file chooser" (for opening or saving files). Thank you for the log, it got me on the right track.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |