Alina

Assigned

No issues.

Reported

MC-164946 Start game crashes on Windows 10 x64 Duplicate

MCPE-39731 After the new Update of Minecraft PE the old Worlds I have do not work anymore I spend a lot of time on them and would like to still be able to play them can you see if you can fix this bug? It‘s also with my Friends Minecraft. Duplicate

Comments

Alina on MC-164946 2019-11-07T16:48:38Z

I am confirming the username renaming from Ştefan to stefan fixes the issue.

So I guess Minecraft should consider using SIDs instead of usernames, or Unicode for handling paths.

Alina on MC-164946 2019-11-07T13:23:04Z

Will check as soon as I will get back to the computer.

Meanwhile, I am thinking: can it be related to username? The Windows user name where I have this error is Ştefan (U+015E Latin Capital Letter S With Cedilla). Maybe there is some IPC code that does not translate correctly between unicode and ANSI, fails to compose some string etc. ? Can this be a cause?

Alina on MC-164946 2019-11-07T12:00:21Z

"The only thing after crash that appears is an empty debug.log file"

The debug.log obtained last time is empty. The content of the first one is in the comment #1.

Alina on MC-164946 2019-11-07T09:22:36Z

What does it means the whole log? I specified in the comment #2 there is no log among those asked in comment #1.

Is there any other log file you want me to attach here?

Alina on MC-164946 2019-11-06T17:09:09Z

The issue still persist with the latest downloaded launcher from your website.

About your comments:

There is no subdirectory crash-reports/ nor launcher_log.txt file.

The only thing after crash that appears is an empty debug.log file (created by libcef.dll), in the installation directory (tested just now with default installation in D:\Minecraft, downloaded Java for Windows version 1,14,0).

Versions:

Launcher 2.1.5964 (2d12ae3b04458774a644a7bb7a3745a624f3ce46)

Bootstrap 601 (eb0baaa31a32c94aa60c82dca8abf285b476f18c)

UI 1314 (373b9dfcd01a47d4a56a375fc8698326d8398671)

The option for automatic sending crash reports to Mojang is activated. You should see the uploaded crash files on your server.

I suggest you to reopen the issue, or to pinpoint me perhaps to some custom options that might help. I would try to run this under WinDBG, but not having the PDB symbols (or the crash being inside Java VM which I have no experience with) limits me on showing at least a meaningful callstack.