为什么Chrome Java更新程序在64位机器上安装全局32位JRE? [英] Why does Chrome Java updater installs a global 32bit JRE on a 64bit machine?
问题描述
显而易见的是Oracle(使用Java8)替代了旧技术 - 在system32(用于64位应用程序)中使用java启动器。 SysWOW64(用于32位应用程序) - 采用这种新方法。但是,在这些位置,还有旧java.exe / javaw.exe / javaws.exe,特别是实际版本(与新的符号链接相同的文件日期)。
我的问题是:
a)在64位机器上安装全局32位JRE的原因是什么?
b)有没有更好的方法来解决问题,而不是删除新的路径条目?
Chrome开发人员懒惰,不想浪费时间找出如何使用完整的64位指令,寄存器等。
Recently I updated the JRE through the update process which chrome (Version 38.0.2125.104 m) offers ("your java is outdated and needs an update" or similar). The result was that my eclipse luna (64 bit) did not execute anymore. Looking closer to the background I detected: the chrome java updater (notabene started from an Oracle site) added C:\ProgramData\Oracle\Java\javapath in front of the env var PATH. This folder contains three symbolic links to the newest java 8 JRE installation in (x86) program folder -> hence to a 32 bit java JRE.
Obviously Oracle replaced (with Java8) the old technique - having the java launchers in system32 (for 64bit applications) resp. SysWOW64 (for 32bit applications) - with this new approach. But: In these locations there still are the "old" java.exe/javaw.exe/javaws.exe, notably also actual versions (same file date as the new symlinks).
My questions are: a) what is the reason for installing a global 32bit JRE on a 64bit machine? b) Is there a better approach to solve the problem than just deleting the new path entry?
Chrome developers are lazy and don't want to waste time finding out how to use full 64-bit instructions, registers etc.
这篇关于为什么Chrome Java更新程序在64位机器上安装全局32位JRE?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!