Open AnrDaemon opened 4 years ago
Are you sure that you aren't running amidst in a zip file or something similar? If you're completely certain that the jar exists in the right path, then I'll take a look at the code and see if there's anything wrong with it.
100% sure. :)
I'll be glad to help you collect more info, if you can help me through it.
The only thing that I can think of is that the directory isn't being parsed correctly. You're 100% certain that the exact directory exists?
It's the same directory that 3.7 and 4.4 opening just fine.
Any news? Or any more data I can provide?
Do you need any more data? I have to use 4.4 for the time being. :(
Do versions other than 1.7.10 work?
What did you do the the loading process, that it suddenly unable to read files?
From 4.4 to 4.6 we switched all of the code to use the Path
object rather than the File
object. This could possibly cause some issues, but it's very strange because typically Path
has better compatibility. With the adoption of Path
, we couldn't use the ZipFile
class anymore. We switched to using the much more finicky ZipFileSystem
, which required us to convert the Path
to a URI
before we can locate the jar. I found multiple bug reports for the JDK stating that there may be an issue with Java when converting the URI
back to a Path
. I made a PR (#951) that should fix this bug, but I'm not entirely sure because I have no way of testing it. If you want, I can make a build of the program that you can use to test if the PR actually fixed it or not.
Yes please. Or I could walk you through creation of a similar directory setup to reproduce the issue, if you have Windows system to test. (VM preferable)
Do versions other than 1.7.10 work?
Given that they haven't fixed native launcher yet… I haven't tried, honestly.
@burgerguy ping?
Sorry about that, here's a build of that branch that the PR is under.
MD5 Hash: d2691fe794e6e2be2f95a858010c2df9 VirusTotal: https://www.virustotal.com/gui/file/34986e5dfeb84b71ecfa33d68c0e78c73c72988797ecd4ae7f6c7589e2727d82/
Let me know if it works. If it doesn't, you can post the crash log here so we can see if it's any different.
Sorry for email spam. I will reboot and retest again more thoroughly. I have an idea of what was changed.
Yes. I had to remove my directory setup because of that MC launcher bug, and it fixed AMIDST as well.
The short version is that Java freak out if realpath resolution end up in UNC volume name. I can write a long version, but I don't think it's warranted given I can't revert setup easily. (Moving profile directory is not easy.)
I'm trying to run freshly downloaded 4.6 JAR, but to no avail.
The file exists, and is a regular 1.7.10 binary. The 4.4 version runs fine with the same profile. 4.5/4.6 crashes as shown.