On Fri, 16 Oct 2020 17:59:14 GMT, Andy Herrick wrote:
> JDK-8254843: Exception launching app on windows in some cases
> loading splashscreen.dll in WinLaunchercpp would load java.dll from path
> instead of runtime/bin causing jni launcher to
> crash. instead we just use what used to be the fallb
On Fri, 16 Oct 2020 23:31:24 GMT, Alexander Matveev
wrote:
>> JDK-8254843: Exception launching app on windows in some cases
>> loading splashscreen.dll in WinLaunchercpp would load java.dll from path
>> instead of runtime/bin causing jni launcher to
>> crash. instead we just use what used to be
On Fri, 16 Oct 2020 17:59:14 GMT, Andy Herrick wrote:
> JDK-8254843: Exception launching app on windows in some cases
> loading splashscreen.dll in WinLaunchercpp would load java.dll from path
> instead of runtime/bin causing jni launcher to
> crash. instead we just use what used to be the fallb
On Fri, 16 Oct 2020 17:59:14 GMT, Andy Herrick wrote:
> JDK-8254843: Exception launching app on windows in some cases
> loading splashscreen.dll in WinLaunchercpp would load java.dll from path
> instead of runtime/bin causing jni launcher to
> crash. instead we just use what used to be the fallb
On Fri, 16 Oct 2020 17:59:14 GMT, Andy Herrick wrote:
> JDK-8254843: Exception launching app on windows in some cases
> loading splashscreen.dll in WinLaunchercpp would load java.dll from path
> instead of runtime/bin causing jni launcher to
> crash. instead we just use what used to be the fallb
JDK-8254843: Exception launching app on windows in some cases
loading splashscreen.dll in WinLaunchercpp would load java.dll from path
instead of runtime/bin causing jni launcher to
crash. instead we just use what used to be the fallback, using
loadDllWithAddDllDirectory().
-
Commit
