Recaf crashes due to path lookup failure via Powershell/Directories-JVM
See original GitHub issueDescribe the bug
Can’t run the recaf-2.7.0-J8-jar-with-dependencies.jar with corretto-11.0.8.10.1 on Windows 10.
To Reproduce
Steps to reproduce the behavior:
- java -jar recaf-2.7.0-J8-jar-with-dependencies.jar
- See error
Exception
If applicable, add the exception/stacktrace.
Exception in thread "main" java.lang.ExceptionInInitializerError
at me.coley.recaf.Recaf.init(Recaf.java:75)
at me.coley.recaf.Recaf.main(Recaf.java:45)
Caused by: java.lang.NullPointerException
at java.base/sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:98)
at java.base/sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)
at java.base/sun.nio.fs.WindowsPath.parse(WindowsPath.java:92)
at java.base/sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:229)
at java.base/java.nio.file.Path.of(Path.java:147)
at java.base/java.nio.file.Paths.get(Paths.java:69)
at me.coley.recaf.Recaf.getDirectory(Recaf.java:167)
at me.coley.recaf.Recaf.getDirectory(Recaf.java:177)
at me.coley.recaf.util.self.SelfDependencyPatcher.<clinit>(SelfDependencyPatcher.java:28)
... 2 more
Screenshots
If applicable, add screenshots to help explain your problem.
Issue Analytics
- State:
- Created 3 years ago
- Comments:12 (5 by maintainers)
Top Results From Across the Web
The modern Java bytecode editor - JavaRepos
Recaf crashes due to path lookup failure via Powershell/Directories-JVM. Describe the bug. Can't run the recaf-2.7.0-J8-jar-with-dependencies.jar with ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I have released versions 22 and 23 which hopefully address this issue.
Version 22 make the library not throw an exception if there is an issue, and version 23 tries to be a bit sneakier trying to retrieve the values. Use 23, but if there are issues with the approach you can fall back to 22, while we have a new look at the problem.
Closing as this has been resolved for the mostpart