Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-98788

issues with running the new 1.9 release

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Awaiting Response
    • None
    • Minecraft 1.9
    • None
    • loading Minecraft then screen goes black and crashes
    • Unconfirmed

      Here is the source of this happeningCompletely ignored arguments: [--nativeLauncherVersion, 301]
      [07:32:28] [Client thread/INFO]: Setting user: RhydTech
      [07:32:28] [Client thread/INFO]: (Session ID is token:16efeb287a4a491187d800af8d02e283:f9b06ce62cdb4260a20b0a2481383cff)
      [07:32:31] [Client thread/INFO]: LWJGL Version: 2.9.4
      [07:32:32] [Client thread/INFO]: Reloading ResourceManager: Default
      #

      1. A fatal error has been detected by the Java Runtime Environment:
        #
      2. EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ff974480398, pid=4656, tid=7220
        #
      3. JRE version: Java(TM) SE Runtime Environment (8.0_25-b18) (build 1.8.0_25-b18)
      4. Java VM: Java HotSpot(TM) 64-Bit Server VM (25.25-b02 mixed mode windows-amd64 compressed oops)
      5. Problematic frame:
      6. C 0x00007ff974480398
        #
      7. Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
        #
      8. An error report file with more information is saved as:
      9. C:\Users\Rhydian\AppData\Roaming\.minecraft\hs_err_pid4656.log
        #
      10. If you would like to submit a bug report, please visit:
      11. http://bugreport.sun.com/bugreport/crash.jsp
      12. The crash happened outside the Java Virtual Machine in native code.
      13. See problematic frame for where to report the bug.
        #
        Java HotSpot(TM) 64-Bit Server VM warning: Using incremental CMS is deprecated and will likely be removed in a future release

            Unassigned Unassigned
            RhydTech Rhydian Paterson
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: