After starting the game the output log viewer stays open for a short while in the main menu and then crashes with a Windows error. Upon clicking on debug it says that "An unhandled win32 exception occured in MinecraftLauncher.exe [3744]." The process seems to also be the same as the one that uses a lot of cpu performance before the crash occurs. After the crash the output log viewer window stays open but doesn't respond anymore.
The nativelog doesn't seem to contain any errors but I'll add it anyways.
Attachments
Comments 10
~Just so you know, this update for the log output was for making it work with modded minecrafts (Forge ect)
I also found the log output overload the Memory utile it crash. Or sometime it drop dramatically to only few MegaByte and it repeat utile it crash.
Here a screenshot of the Memory Overload a short time before it crash:
*The Log Output take more memory than Minecraft... Nice! ._.
Like the main post, at the end of the live of the log output, it was costing 1 heart of my CPU.
*You can attache this screenshot
Log Output overload the memory on it self utile it crash
http://image.noelshack.com/fichiers/2017/17/1493258679-bandicam-2017-04-26-22-00-08-549.jpg
Whoa, additional info:
The log file viewer crashes even if you're not in the game, doing nothing, so nothing is added to the log. Running the program, but staying at the splash screen is quite sufficient for the log file viewer to crash after approximately between 10 and 30 minutes…
(i7/3.5MHz/16GB RAM/GeForce 4GB/Win10/MC V.1.12/vanilla)
Log file content:
[23:19:33] [Client thread/INFO]: Setting user: dscheJOuh
[23:19:34] [Client thread/INFO]: LWJGL Version: 2.9.4
[23:19:35] [Client thread/INFO]: Reloading ResourceManager: Default
[23:19:35] [Sound Library Loader/INFO]: Starting up SoundSystem...
[23:19:36] [Thread-3/INFO]: Initializing LWJGL OpenAL
[23:19:36] [Thread-3/INFO]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
[23:19:36] [Thread-3/INFO]: OpenAL initialized.
[23:19:36] [Sound Library Loader/INFO]: Sound engine started
[23:19:38] [Client thread/INFO]: Created: 1024x512 textures-atlas
[23:19:39] [Client thread/INFO]: Narrator library for x64 successfully loaded
^ End log file, here it had crashed when I came back after approximately 30 minutes.
O.K., the latest update of the Minecraft Launcher to v.2.0.934 seems to have fixed the issue for me for now.
Do any others still have this problem?
Yes, this is fixed. I play with mods right now with no issue of cpu or memory overload !
~Bug Patched
------------------------
Edit: (NEW) The Log Output crashed but it took way more time before it crash.
Same sort of reason for the crash (msg from Window saying it stopped to work....)
Almost the same:
Log viewer ("Minecraft game output" window) works properly for some time, but after several lines stops adding new lines (no more information on what happens/goes wrong in the game) and shows no further reaction (buttons ineffective).
After some more time, the log window goes completely blank.
It also seems there are no more lines being added in the log files (in \logs).
NEW since launcher update to 2.0.847 (worked properly before)
Win 10/MC1.11.2/v
[EDIT]: Additional info:
Happens in ANY game now after a certain time.
Often, the moment the log crashes, the game goes into pause mode.
Same on new system (i7/3.5MHz/16GB RAM/GeForce 4GB/Win10/MC V.1.11.2/vanilla)