Uploaded image for project: 'Minecraft Launcher'
  1. Minecraft Launcher
  2. MCL-1396

"Fake" javaw.exe processes/javaw.exe eating enormous amounts of memory

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Resolution: Duplicate
    • Affects Version/s: 1.2
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Environment:
      Java 1.7.0_25 64 bit
      Windows Vista
      Graphics Card: ATI Radeon HD 4350
    • Confirmation Status:
      Unconfirmed

      Description

      I have a feeling this has to do with the ninja fix to "trick" the Intel Drivers for performance.
      Basically, opening Minecraft will inconsistently (sometimes it happens, sometimes it doesn't) open up 3 javaw.exe processes viewable from the Task Manager. Normally, it opens two; the javaw.exe for the launcher and the javaw.exe for the game. This third, fake process eats CPU usage and memory like...well to be honest the only analogies I can come up with are either offensive or so out of mainstream culture so...basically at it's worst, the fake javaw was using 96% of the CPU and over a million KB of memory. It has since died down this behavior and capped itself around 800,000 KB and 25% of the CPU, but this is still a lot. Ending the fake process does nothing visible to affect the game.
      Attached are screenshots of my Task Manager.

      Edit for August 1st, 2013: I have so far been unable to reproduce the fake javaw process. However, I have identified that the one eating the CPU isn't the fake process, but the launcher.

        Attachments

        1. Fake1.gif
          Fake1.gif
          34 kB
        2. Fake2.gif
          Fake2.gif
          36 kB
        3. Fake3.gif
          Fake3.gif
          34 kB
        4. Fake4.gif
          Fake4.gif
          35 kB
        5. Million.gif
          Million.gif
          68 kB

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                neospector Neospector
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Potential Duplicates