How do I prevent frequent crashes when using simulink (R2014b)?

Running Simulink on my system:

>> ver

----------------------------------------------------------------------------------------------------

MATLAB Version: 8.4.0.150421 (R2014b) MATLAB License Number: 329139 Operating System: Microsoft Windows 7 Professional Version 6.1 (Build 7601: Service Pack 1) Java Version: Java 1.7.0_11-b21 with Oracle Corporation Java HotSpot™ 64-Bit Server VM mixed mode

----------------------------------------------------------------------------------------------------

I, at least once a day, experience a Matlab crash (when actually clicking on the run button in Simulink).

I looked up the attached crash reports (matlab_crash_dump.7356-1 and hs_error_pid7356.log). The latter stating that:

1. A fatal error has been detected by the Java Runtime Environment:#
2. EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00000000e09fcc9a, pid=7356, tid=9824#
3. JRE version: 7.0_11-b21
4. Java VM: Java HotSpot™ 64-Bit Server VM (23.6-b04 mixed mode windows-amd64 compressed oops)
5. Problematic frame:
6. C 0x00000000e09fcc9a#
7. Failed to write core dump. Minidumps are not enabled by default on client versions of Windows#
8. If you would like to submit a bug report, please visit:
9. http://bugreport.sun.com/bugreport/crash.jsp
10. The crash happened outside the Java Virtual Machine in native code.
11. See problematic frame for where to report the bug.#

According to Java (32 bit) I've installed the latest update.

Might having installed a 32 version on a 64 bit machine cause problems?

Your help is much apreciated

Kind regards

Cornelis

[Cesar Rivadeneyra]

Cornelis,

Have you tried reaching out to MathWorks Technical Support?

Given the frequency of crashes you may want to call them:

Technical Support 508-647-7000

Other options are here:

http://www.mathworks.com/support/contact_us/

[Philip Borghesani]

This does not look like a Java problem. Can you post or attach the first 20 or so frames from the files matlab_crash_dump.7356-0 and matlab_crash_dump.7356-1?

Are your display drivers up to date?

[Cornelis]

Dear Philip,

thanks for your reply. I cannot locate the -0 file but here are the first 25 frames from matlab_crash_dump.7356-1

   -  
------------------------------------------------------------------------

             Assertion detected at Mon Dec 01 13:39:49 2014
------------------------------------------------------------------------

Configuration:

Crash Decoding     : Disabled
Default Encoding   : windows-1252
Graphics card 1    : Intel Corporation ( 0x8086 ) Intel(R) HD Graphics 4000 Version 8.15.10.2639
Graphics card 2    : NVIDIA ( 0x10de ) NVIDIA Quadro K1000M    Version 9.18.13.2762
Java Crash Report  : C:\Users\Cornelis\AppData\Local\Temp\hs_error_pid7356.log
MATLAB Architecture: win64
MATLAB Root        : C:\Program Files\MATLAB\R2014b
MATLAB Version     : 8.4.0.150421 (R2014b)
Operating System   : Microsoft Windows 7 Professional 
Processor ID       : x86 Family 6 Model 58 Stepping 9, GenuineIntel
Software OpenGL    : 0
Virtual Machine    : Java 1.7.0_11-b21 with Oracle Corporation Java HotSpot(TM) 64-Bit Server VM mixed mode
Window System      : Version 6.1 (Build 7601: Service Pack 1)

Fault Count: 1

Assertion in void __cdecl `anonymous-namespace'::mwJavaAbort(void) at b:\matlab\src\jmi\javainit.cpp line 1319: Fatal Java Exception. See Java Crash Report for details.

According to: NVIDIA Quadro K1000M > properies > Driver > update driver: "the best sofware for your device is already installed. Windows has determined the driver software for your devise is up to date".

Thanks for your help in this!

[Andreas Goser]

Cornelis, I see you created a support request today. I have asked an engineer in your country to contact you today.

Answer 1

[Philip Borghesani]

Having a 32 bit version of Java on the machine will not cause problems. Whether or not Java is up to date is not important. If you look at the output of ver and your crash info you will notice that MATLAB is using the 64 bit Java that shipped with MATLAB. That is a good thing and is not likely to be the cause of the problem.