JVM 32-bit crashes on a 64-bit machine

Question

In my JVM Java application (1.6.0_26, 32-bit), a sporadic crash occurred while closing this Java application. This intermittent JVM crash issue apparently only affects 64-bit Windows. This problem does NOT occur on 32-bit Windows and Mac OS X. Can someone tell me the reason for this. in fact, this Java application uses the 100-150 libraries and it does not crash at runtime as soon as the application receives a closed failure. Is it appropriate to use a 32-bit JVM on a 64-bit machine?

Many thanks for your help.

Answer 1

Short answer no. Using a 32-bit JVM on a 64-bit machine is not recommended. The longer answer is that Windows 64-bit can run 32-bit programs in compatibility mode if you don’t have the option.

You really don't need to do this, since the 64-bit JVM works fine on Windows. It also means that your process can use more memory and speed than a 32-bit process can use.

http://msdn.microsoft.com/en-us/library/aa384249(v=vs.85).aspx

Answer 2

Having a similar problem, when I installed my JBM 32-bit bit on 64-bit Win7, everything worked fine until the third-person OLE modem was loaded. The JVM provided a crash report stating that the Java binary has stopped working and Message in the crash report code number is HEAP_MEMORY_CORRUPTION. This is rather strange, because when I attached the profiler, the heap was under the maximum limit. I suspect that my Bridge provider has done some kernel-mode actions (if possible) that are not allowed during emulation under WOW64.

I decided mine. When ole filled with MS Office, it could not fill 2007 instead, when I installed 2003, it worked. make sure your application crashes immediately or when some native calls occur, this way you can identify the problem.