When I made postprocessing script and then simulation is ok. Next step in postprocessing there is a matlab error....
The below is report
MATLAB crash file:C:\Users\user\AppData\Local\Temp\matlab_crash_dump.24412-1:
--------------------------------------------------------------------------------
Access violation detected at 목 10 04 02:23:07 2018 +0900
--------------------------------------------------------------------------------
Configuration:
Crash Decoding : Disabled - No sandbox or build area path
Crash Mode : continue (default)
Default Encoding : KSC_5601
Deployed : false
Graphics Driver : NVIDIA Corporation GeForce GTX 1050/PCIe/SSE2 Version 4.6.0 NVIDIA 388.13
Graphics card 1 : NVIDIA ( 0x10de ) NVIDIA GeForce GTX 1050 Version 23.21.13.8813 (2017-10-27)
Java Version : Java 1.8.0_144-b01 with Oracle Corporation Java HotSpot(TM) 64-Bit Server VM mixed mode
MATLAB Architecture : win64
MATLAB Entitlement ID : 1341897
MATLAB Root : C:\Program Files\MATLAB\R2018a
MATLAB Version : 9.4.0.813654 (R2018a)
OpenGL : hardware
Operating System : Microsoft Windows 10 Pro
Process ID : 24412
Processor ID : x86 Family 6 Model 158 Stepping 9, GenuineIntel
Session Key : aed9cd70-6644-4d2a-b919-35c0c06f8d93
Window System : Version 10.0 (Build 17134)
Fault Count: 1
Abnormal termination
Register State (from fault):
RAX = 00000000043f92a0 RBX = 000000000000004d
RCX = 00000000062543b4 RDX = 0000000000000000
RSP = 00000000043f9220 RBP = 00000000043f9378
RSI = 000000000591f7b0 RDI = 0000000000000000
R8 = 553250434c646142 R9 = 00007ffa4b190000
R10 = 00000000043f91e8 R11 = 00000000043f92d8
R12 = 0000000000000000 R13 = 00007ffa49796068
R14 = 0000000000000000 R15 = 00000000043f9570
RIP = 00000000061f51a0 EFL = 00010202
CS = 0033 FS = 0053 GS = 002b
Stack Trace (from fault):
[ 0] 0x00000000061f51a0 bin\win64\libemlrt.dll+00217504 emlrtInitCharArrayR2013a+00000128
[ 1] 0x00007ffa49792433 C:\Users\user\Documents\MATLAB\Add-Ons\Apps\Abaqus2Matlab_GUI_v01\code\files\odb\exploreFieldOdbPyScript.mexw64+00009267 exploreFieldOdbPyScript+00004963
[ 2] 0x00007ffa497941bc C:\Users\user\Documents\MATLAB\Add-Ons\Apps\Abaqus2Matlab_GUI_v01\code\files\odb\exploreFieldOdbPyScript.mexw64+00016828 exploreFieldOdbPyScript+00012524
[ 3] 0x00007ffa4979446a C:\Users\user\Documents\MATLAB\Add-Ons\Apps\Abaqus2Matlab_GUI_v01\code\files\odb\exploreFieldOdbPyScript.mexw64+00017514 exploreFieldOdbPyScript+00013210
[ 4] 0x00000000fc626594 bin\win64\libmex.dll+00288148 MexRetrieveVersion+00002916
[ 5] 0x00000000fc62678c bin\win64\libmex.dll+00288652 MexRetrieveVersion+00003420
[ 6] 0x00000000fc6268de bin\win64\libmex.dll+00288990 MexRetrieveVersion+00003758
[ 7] 0x00000000fc612ec3 bin\win64\libmex.dll+00208579 mexUnlock_800+00024147
[ 8] 0x000000001a60c51a bin\win64\pgo\m_dispatcher.dll+00050458 Mfh_file::dispatch_fh_impl+00001114
[ 9] 0x000000001a60c0b2 bin\win64\pgo\m_dispatcher.dll+00049330 Mfh_file::dispatch_fh+00000062
[ 10] 0x000000001a604674 bin\win64\pgo\m_dispatcher.dll+00018036 Mfunction_handle::dispatch+00000420
[ 11] 0x000000001b522aa1 bin\win64\pgo\m_lxe.dll+00404129
[ 12] 0x000000001b5a8e25 bin\win64\pgo\m_lxe.dll+00953893 mwboost::serialization::singleton<mwboost::archive::detail::pointer_iserializer<mwboost::archive::binaryTerm_iarchive,ir::IrTree> >::get_instance+00115205
[ 13] 0x000000001b5aa808 bin\win64\pgo\m_lxe.dll+00960520 mwboost::serialization::singleton<mwboost::archive::detail::pointer_iserializer<mwboost::archive::binaryTerm_iarchive,ir::IrTree> >::get_instance+00121832
[ 14] 0x000000001b5ab403 bin\win64\pgo\m_lxe.dll+00963587 mwboost::serialization::singleton<mwboost::archive::detail::pointer_iserializer<mwboost::archive::binaryTerm_iarchive,ir::IrTree> >::get_instance+00124899
[ 15] 0x000000001b5ac836 bin\win64\pgo\m_lxe.dll+00968758 mwboost::serialization::singleton<mwboost::archive::detail::pointer_iserializer<mwboost::archive::binaryTerm_iarchive,ir::IrTree> >::get_instance+00130070
[ 16] 0x000000001b5ad3f0 bin\win64\pgo\m_lxe.dll+00971760 mwboost::serialization::singleton<mwboost::archive::detail::pointer_iserializer<mwboost::archive::binaryTerm_iarchive,ir::IrTree> >::get_instance+00133072
[ 17] 0x000000001b5ac97f bin\win64\pgo\m_lxe.dll+00969087 mwboost::serialization::singleton<mwboost::archive::detail::pointer_iserializer<mwboost::archive::binaryTerm_iarchive,ir::IrTree> >::get_instance+00130399
[ 18] 0x000000001b5aca7e bin\win64\pgo\m_lxe.dll+00969342 mwboost::serialization::singleton<mwboost::archive::detail::pointer_iserializer<mwboost::archive::binaryTerm_iarchive,ir::IrTree> >::get_instance+00130654
[ 19] 0x000000001b52e8a5 bin\win64\pgo\m_lxe.dll+00452773
[ 20] 0x000000001b52b335 bin\win64\pgo\m_lxe.dll+00439093
[ 21] 0x000000001b52a82e bin\win64\pgo\m_lxe.dll+00436270
[ 22] 0x000000001b528b35 bin\win64\pgo\m_lxe.dll+00428853
[ 23] 0x000000001b528e9e bin\win64\pgo\m_lxe.dll+00429726
[ 24] 0x000000001b528e29 bin\win64\pgo\m_lxe.dll+00429609
[ 25] 0x000000001a60c51a bin\win64\pgo\m_dispatcher.dll+00050458 Mfh_file::dispatch_fh_impl+00001114
[ 26] 0x000000001a60c0b2 bin\win64\pgo\m_dispatcher.dll+00049330 Mfh_file::dispatch_fh+00000062
[ 27] 0x000000001a604674 bin\win64\pgo\m_dispatcher.dll+00018036 Mfunction_handle::dispatch+00000420
[ 28] 0x000000001b522aa1 bin\win64\pgo\m_lxe.dll+00404129
[ 29] 0x000000001b5a8e25 bin\win64\pgo\m_lxe.dll+00953893 mwboost::serialization::singleton<mwboost::archive::detail::pointer_iserializer<mwboost::archive::binaryTerm_iarchive,ir::IrTree> >::get_instance+00115205
[ 30] 0x000000001b5aa808 bin\win64\pgo\m_lxe.dll+00960520 mwboost::serialization::singleton<mwboost::archive::detail::pointer_iserializer<mwboost::archive::binaryTerm_iarchive,ir::IrTree> >::get_instance+00121832
[ 31] 0x000000001b5ab403 bin\win64\pgo\m_lxe.dll+00963587 mwboost::serialization::singleton<mwboost::archive::detail::pointer_iserializer<mwboost::archive::binaryTerm_iarchive,ir::IrTree> >::get_instance+00124899
[ 32] 0x000000001b5ac836 bin\win64\pgo\m_lxe.dll+00968758 mwboost::serialization::singleton<mwboost::archive::detail::pointer_iserializer<mwboost::archive::binaryTerm_iarchive,ir::IrTree> >::get_instance+00130070
[ 33] 0x000000001b5ad3f0 bin\win64\pgo\m_lxe.dll+00971760 mwboost::serialization::singleton<mwboost::archive::detail::pointer_iserializer<mwboost::archive::binaryTerm_iarchive,ir::IrTree> >::get_instance+00133072
[ 34] 0x000000001b5ac97f bin\win64\pgo\m_lxe.dll+00969087 mwboost::serialization::singleton<mwboost::archive::detail::pointer_iserializer<mwboost::archive::binaryTerm_iarchive,ir::IrTree> >::get_instance+00130399
[ 35] 0x000000001b5aca7e bin\win64\pgo\m_lxe.dll+00969342 mwboost::serialization::singleton<mwboost::archive::detail::pointer_iserializer<mwboost::archive::binaryTerm_iarchive,ir::IrTree> >::get_instance+00130654
[ 36] 0x000000001b52e8a5 bin\win64\pgo\m_lxe.dll+00452773
[ 37] 0x000000001b52b335 bin\win64\pgo\m_lxe.dll+00439093
[ 38] 0x000000001b52a82e bin\win64\pgo\m_lxe.dll+00436270
[ 39] 0x000000001b531b9a bin\win64\pgo\m_lxe.dll+00465818
[ 40] 0x000000001b53133d bin\win64\pgo\m_lxe.dll+00463677
[ 41] 0x000000001b53144e bin\win64\pgo\m_lxe.dll+00463950
[ 42] 0x000000001b6d1d9c bin\win64\pgo\m_lxe.dll+02170268 mwboost::serialization::singleton<mwboost::archive::detail::pointer_oserializer<mwboost::archive::binary_oarchive,MathWorks::lxe::PreLineExecutionEvent> >::get_instance+00475644
[ 43] 0x000000001b6d1d4a bin\win64\pgo\m_lxe.dll+02170186 mwboost::serialization::singleton<mwboost::archive::detail::pointer_oserializer<mwboost::archive::binary_oarchive,MathWorks::lxe::PreLineExecutionEvent> >::get_instance+00475562
[ 44] 0x000000001b50051d bin\win64\pgo\m_lxe.dll+00263453
[ 45] 0x000000001a818acf bin\win64\pgo\m_interpreter.dll+00297679 inEvalCmdWithLocalReturn+00000063
[ 46] 0x00000000fb60bedb bin\win64\libmwbridge.dll+00114395 mnParser+00001595
[ 47] 0x000000001a456564 bin\win64\mcr.dll+00222564 mcr::runtime::setInterpreterThreadSingletonToCurrent+00091332
[ 48] 0x000000001a4597ae bin\win64\mcr.dll+00235438 mcr::runtime::setInterpreterThreadSingletonToCurrent+00104206
[ 49] 0x000000001a476c8a bin\win64\mcr.dll+00355466 mcrRegisterExternalFunction+00007930
[ 50] 0x000000001a4789bc bin\win64\mcr.dll+00362940 mcrRegisterExternalFunction+00015404
[ 51] 0x000000001a475bff bin\win64\mcr.dll+00351231 mcrRegisterExternalFunction+00003695
[ 52] 0x000000001a476c46 bin\win64\mcr.dll+00355398 mcrRegisterExternalFunction+00007862
[ 53] 0x000000001a475ce3 bin\win64\mcr.dll+00351459 mcrRegisterExternalFunction+00003923
[ 54] 0x000000001a478ff6 bin\win64\mcr.dll+00364534 mcrRegisterExternalFunction+00016998
[ 55] 0x00000000fd014f67 bin\win64\iqm.dll+00544615 iqm::IqmPlugin<cmddistributor::PackagedTaskIIP>::getIIP+00016215
[ 56] 0x00000000fd01567f bin\win64\iqm.dll+00546431 iqm::PackagedTaskPlugin::execute+00000911
[ 57] 0x00000000fd014fed bin\win64\iqm.dll+00544749 iqm::IqmPlugin<cmddistributor::PackagedTaskIIP>::getIIP+00016349
[ 58] 0x00000000fd0154c3 bin\win64\iqm.dll+00545987 iqm::PackagedTaskPlugin::execute+00000467
[ 59] 0x00000000fcfed9ea bin\win64\iqm.dll+00383466 iqm::Iqm::setupIqmFcnPtrs+00071994
[ 60] 0x00000000fcfed84c bin\win64\iqm.dll+00383052 iqm::Iqm::setupIqmFcnPtrs+00071580
[ 61] 0x00000000fcfce722 bin\win64\iqm.dll+00255778 iqm::Iqm::deliver+00003730
[ 62] 0x00000000fcfcf749 bin\win64\iqm.dll+00259913 iqm::Iqm::deliver+00007865
[ 63] 0x00000001001aa211 bin\win64\libmwservices.dll+01810961 services::system_events::PpeDispatchHook::dispatchOne+00030865
[ 64] 0x00000001001b7ff3 bin\win64\libmwservices.dll+01867763 sysq::addProcessPendingEventsUnitTestHook+00004659
[ 65] 0x00000001001b81e0 bin\win64\libmwservices.dll+01868256 sysq::addProcessPendingEventsUnitTestHook+00005152
[ 66] 0x00000001001b9576 bin\win64\libmwservices.dll+01873270 sysq::getCondition+00003446
[ 67] 0x00000001001bb0e6 bin\win64\libmwservices.dll+01880294 svWS_ProcessPendingEvents+00000230
[ 68] 0x000000001a460737 bin\win64\mcr.dll+00263991 mcr::runtime::setInterpreterThreadSingletonToCurrent+00132759
[ 69] 0x000000001a462360 bin\win64\mcr.dll+00271200 mcr::runtime::setInterpreterThreadSingletonToCurrent+00139968
[ 70] 0x000000001a43e9b7 bin\win64\mcr.dll+00125367 mcr_process_events+00001959
[ 71] 0x000000001a30fef5 bin\win64\MVMLocal.dll+00327413 mvm_server::inproc::LocalFactory::terminate+00139589
[ 72] 0x00000000fa9605b9 bin\win64\mvm.dll+01246649 mvm::detail::initLocalMvmHack+00000793
[ 73] 0x00000000fa960dcb bin\win64\mvm.dll+01248715 mvm::detail::SessionImpl::privateSession+00000555
[ 74] 0x00000000fa960ff1 bin\win64\mvm.dll+01249265 mvm::detail::SessionImpl::privateSession+00001105
[ 75] 0x000000014000780d bin\win64\MATLAB.exe+00030733
[ 76] 0x000000014000862f bin\win64\MATLAB.exe+00034351
[ 77] 0x00007ffa5e063034 C:\WINDOWS\System32\KERNEL32.DLL+00077876 BaseThreadInitThunk+00000020
[ 78] 0x00007ffa60431461 C:\WINDOWS\SYSTEM32\ntdll.dll+00463969 RtlUserThreadStart+00000033
This error was detected while a MEX-file was running. If the MEX-file
is not an official MathWorks function, please examine its source code
for errors. Please consult the External Interfaces Guide for information
on debugging MEX-files.
How can i fix it??
Could you send me your files in a p.m. to run them and try to fix the problem?
Confidentiality in the various files shared is explicitly declared.
Thanks,
George
I can't understand your first and fourth reply (1) and (4). (2) and (3) do not matter, it is working but (1) is 0 logical value.
Also I have something strange, I ran it again after the error occurred.
<matlab command window>
Script_abaqus2matlabtest2_A2M
Simulation Started
Intel(R) Fortran Compiler for applications running on Intel(R) 64, Version 10.1.011
Copyright (C) 1985-2007 Intel Corporation. All rights reserved.
Setting environment for IMSL Fortran Library - Intel64
Simulation Finished
Obtaining desired output data by Abaqus2Matlab
Intel(R) Fortran Compiler for applications running on Intel(R) 64, Version 10.1.011
Copyright (C) 1985-2007 Intel Corporation. All rights reserved.
Setting environment for IMSL Fortran Library - Intel64
NO NEED TO UPGRADE. THE OUTPUT DATABASE FILE IS ALREADY UP-TO-DATE
Intel(R) Fortran Compiler for applications running on Intel(R) 64, Version 10.1.011
Copyright (C) 1985-2007 Intel Corporation. All rights reserved.
Setting environment for IMSL Fortran Library - Intel64
Abaqus License Manager checked out the following license:
"cae" release 6.16 from Flexnet server 147.46.120.96
<1 out of 4 licenses remain available>.
And then this state is continuing.
This situation is too long, so i stopped through ctrl+c and then I saw the below error
Interrupt.
Error in rpyRead
Error in exploreFieldOdb (line 153)
Error in Script_abaqus2matlabtest2_A2M (line 59)
out=exploreFieldOdb(odb_name);
I don't know why I have stopped in this situation.
1) This may be due to the multi-threaded environment of Matlab and Java. Matlab for the most part is a single threaded environment. That is, all commands are executed sequentially along a single execution thread. The main exception to this are the Handle Graphics (GUI) components whose operations execute on the Java Event Dispatch Thread (EDT). Matlab normally uses Swing components for the GUIs. All access to Swing components should be done from the event dispatch thread (EDT), to ensure that the operations are executed sequentially. If you need to determine whether your code is running on the event dispatch thread, execute in Matlab the following command:
>> javax.swing.SwingUtilities.isEventDispatchThread
See also the following link:
https://undocumentedmatlab.com/blog/matlab-and-the-event-dispatch-thread-edt
2) There may be a problem with Matlab's browser. What happens when you execute the following:
>> web www.google.com
This command should open a Google search page from MATLAB. If there is a problem then you might get an error with this command.
3) It is possible that the file 'classpath.txt' is shadowed by another file of the same name. To check if this is the case, execute:
>> which classpath.txt
The output must be a single file location that should look similar to the following:
C:\Program Files\MATLAB\R2012a\toolbox\local\classpath.txt
If the file location is different or multiple file locations appear, then the 'classpath.txt' may be shadowed. To resolve this issue, simply rename any 'classpath.txt' files (except for the original Matlab file).
4) See some workarounds in the following link:
https://undocumentedmatlab.com/blog/handling-red-java-console-errors
Please try the above hints and let me know if your problem is solved. In case your problem is solved, please let me know how the problem was fixed.
Best,
George
Hello S. I. Kim,
Please check the following links:
http://abaqus2matlab.wixsite.com/abaqus2matlab/forum/abaqus2matlab-users-forum/matlab-met-a-crash-every-time-i-ran-the-example
http://abaqus2matlab.wixsite.com/abaqus2matlab/forum/abaqus2matlab-users-forum/error-in-running-czm-example
I hope this solves your problem.
Best,
George