Back to the main page.

Bug 3376 - nanmean crashes after Windows update

Status CLOSED WONTFIX
Reported 2017-11-21 14:08:00 +0100
Modified 2019-08-10 12:37:29 +0200
Product: FieldTrip
Component: core
Version: unspecified
Hardware: PC
Operating System: Windows
Importance: P5 critical
Assigned to:
URL:
Tags:
Depends on:
Blocks:
See also:

Stephen Whitmarsh - 2017-11-21 14:08:04 +0100

Hi there, The nanmean .mex function in fieldtrip/external/stats/nanmean.mexq64 now causes windows 10 to crash. I have a very strong suspicion this is the result of the latest windows update (you might have noticed windows updating in the last couple of days). In fact this update locked my computer at home, which took a while to debug. I wanted to know if any of you could replicate this for me (on windows)? If so please start up a new matlab (it will crash in the end): add fieldtrip to your path execute 'ft_defaults' 'which nanmean' to see it's using the fieldtrip nanmean 'nanmean' (this could crash matlab) See MATLAB crash dump below (I replicated on MATLAB 2016b and 2013): ------------------------------------------------------------------------ Access violation detected at Tue Nov 21 12:38:53 2017 ------------------------------------------------------------------------ Configuration: Crash Decoding : Disabled Default Encoding : windows-1252 MATLAB Architecture: win64 MATLAB Root : C:\Program Files\MATLAB\R2013b MATLAB Version : 8.2.0.701 (R2013b) Operating System : Microsoft Windows 8 Processor ID : x86 Family 6 Model 63 Stepping 2, GenuineIntel Virtual Machine : Java 1.7.0_11-b21 with Oracle Corporation Java HotSpot(TM) 64-Bit Server VM mixed mode Window System : Version 6.2 (Build 9200) Fault Count: 1 Abnormal termination: Access violation Register State (from fault): RAX = 00000000671f127f RBX = 00000000043fb290 RCX = 0000000000000000 RDX = 00000000043fb290 RSP = 00000000043fa270 RBP = 00000000043fb190 RSI = 00000000671f67c0 RDI = 00000000043fb190 R8 = 0000000000000000 R9 = 00000000043fb190 R10 = 0000000000000000 R11 = 00000000043fb290 R12 = 0000000000000000 R13 = 0000000067044e40 R14 = 0000000000000000 R15 = 00000000043fb290 RIP = 0000000010684d64 EFL = 00010202 CS = 0033 FS = 0053 GS = 002b Stack Trace (from fault): [ 0] 0x0000000010684d64 C:\Program Files\MATLAB\R2013b\bin\win64\libmx.dll+00019812 mxGetClassID+00000004 [ 1] 0x00007ffe7c271025 D:\fieldtrip-master_21092017\fieldtrip-master\external\stats\nanmean.mexw64+00004133 mexFunction+00000037 [ 2] 0x000000006d76f741 C:\Program Files\MATLAB\R2013b\bin\win64\libmex.dll+00063297 mexRunMexFile+00000129 [ 3] 0x000000006d76e212 C:\Program Files\MATLAB\R2013b\bin\win64\libmex.dll+00057874 inSwapMexfileReader+00000226 [ 4] 0x000000006d76f2c4 C:\Program Files\MATLAB\R2013b\bin\win64\libmex.dll+00062148 _constructor_lm_mexmaci64+00001620 [ 5] 0x000000018000d612 C:\Program Files\MATLAB\R2013b\bin\win64\m_dispatcher.dll+00054802 Mfh_file::dispatch_fh+00000674 [ 6] 0x000000018000defa C:\Program Files\MATLAB\R2013b\bin\win64\m_dispatcher.dll+00057082 Mfunction_handle::dispatch+00000810 [ 7] 0x0000000011096a81 C:\Program Files\MATLAB\R2013b\bin\win64\m_interpreter.dll+00486017 inFunctionHandleInterface::DestroyWorkspace+00308737 [ 8] 0x0000000011120657 C:\Program Files\MATLAB\R2013b\bin\win64\m_interpreter.dll+01050199 inEachVisibleName+00015383 [ 9] 0x00000000110946c2 C:\Program Files\MATLAB\R2013b\bin\win64\m_interpreter.dll+00476866 inFunctionHandleInterface::DestroyWorkspace+00299586 [ 10] 0x000000001107b85f C:\Program Files\MATLAB\R2013b\bin\win64\m_interpreter.dll+00374879 inFunctionHandleInterface::DestroyWorkspace+00197599 [ 11] 0x000000001107b7c8 C:\Program Files\MATLAB\R2013b\bin\win64\m_interpreter.dll+00374728 inFunctionHandleInterface::DestroyWorkspace+00197448 [ 12] 0x000000001109ebbd C:\Program Files\MATLAB\R2013b\bin\win64\m_interpreter.dll+00519101 inFunctionHandleInterface::DestroyWorkspace+00341821 [ 13] 0x000000001109b5cc C:\Program Files\MATLAB\R2013b\bin\win64\m_interpreter.dll+00505292 inFunctionHandleInterface::DestroyWorkspace+00328012 [ 14] 0x000000001107e529 C:\Program Files\MATLAB\R2013b\bin\win64\m_interpreter.dll+00386345 inFunctionHandleInterface::DestroyWorkspace+00209065 [ 15] 0x000000018000d612 C:\Program Files\MATLAB\R2013b\bin\win64\m_dispatcher.dll+00054802 Mfh_file::dispatch_fh+00000674 [ 16] 0x000000018000defa C:\Program Files\MATLAB\R2013b\bin\win64\m_dispatcher.dll+00057082 Mfunction_handle::dispatch+00000810 [ 17] 0x000000001113438e C:\Program Files\MATLAB\R2013b\bin\win64\m_interpreter.dll+01131406 inSetWorkSpaces+00001262 [ 18] 0x00000000111406f5 C:\Program Files\MATLAB\R2013b\bin\win64\m_interpreter.dll+01181429 SetInterpreter+00000325 [ 19] 0x0000000011142cb5 C:\Program Files\MATLAB\R2013b\bin\win64\m_interpreter.dll+01191093 inEvalCmd+00008789 [ 20] 0x0000000011142c82 C:\Program Files\MATLAB\R2013b\bin\win64\m_interpreter.dll+01191042 inEvalCmd+00008738 [ 21] 0x0000000011142c47 C:\Program Files\MATLAB\R2013b\bin\win64\m_interpreter.dll+01190983 inEvalCmd+00008679 [ 22] 0x000000001152ad0c C:\Program Files\MATLAB\R2013b\bin\win64\m_interpreter.dll+05287180 inMexPutVariable+00008364 [ 23] 0x000000001152b066 C:\Program Files\MATLAB\R2013b\bin\win64\m_interpreter.dll+05288038 inMexPutVariable+00009222 [ 24] 0x000000001152b49e C:\Program Files\MATLAB\R2013b\bin\win64\m_interpreter.dll+05289118 inMexPutVariable+00010302 [ 25] 0x000000001152b7dc C:\Program Files\MATLAB\R2013b\bin\win64\m_interpreter.dll+05289948 inMexPutVariable+00011132 [ 26] 0x000000001143ff91 C:\Program Files\MATLAB\R2013b\bin\win64\m_interpreter.dll+04325265 inEvalCmdWithLocalReturn+00000065 [ 27] 0x000000006c71be9d C:\Program Files\MATLAB\R2013b\bin\win64\libmwbridge.dll+00048797 mnDebugPrompt+00000109 [ 28] 0x000000006c71cf7f C:\Program Files\MATLAB\R2013b\bin\win64\libmwbridge.dll+00053119 mnParser+00000735 [ 29] 0x000000006e4ff4b4 C:\Program Files\MATLAB\R2013b\bin\win64\mcr.dll+00193716 mcrInstance::mnParser_on_interpreter_thread+00000036 [ 30] 0x000000006e4e44b0 C:\Program Files\MATLAB\R2013b\bin\win64\mcr.dll+00083120 mcr::runtime::setInterpreterThreadToCurrent+00029472 [ 31] 0x000000006e4e4510 C:\Program Files\MATLAB\R2013b\bin\win64\mcr.dll+00083216 mcr::runtime::setInterpreterThreadToCurrent+00029568 [ 32] 0x000000006b01fa96 C:\Program Files\MATLAB\R2013b\bin\win64\uiw.dll+00391830 UIW_IsUserMessage+00000086 [ 33] 0x000000006b020175 C:\Program Files\MATLAB\R2013b\bin\win64\uiw.dll+00393589 UIW_SetGLIMUserMsg+00000117 [ 34] 0x000000006b0201f9 C:\Program Files\MATLAB\R2013b\bin\win64\uiw.dll+00393721 UIW_SetGLIMUserMsg+00000249 [ 35] 0x00007ffe84162f2b C:\WINDOWS\System32\USER32.dll+00208683 GetUpdatedClipboardFormats+00000683 [ 36] 0x00007ffe84150459 C:\WINDOWS\System32\USER32.dll+00132185 GetPropW+00000665 [ 37] 0x00007ffe841503e6 C:\WINDOWS\System32\USER32.dll+00132070 GetPropW+00000550 [ 38] 0x00007ffe848490a4 C:\WINDOWS\SYSTEM32\ntdll.dll+00692388 KiUserCallbackDispatcher+00000036 [ 39] 0x00007ffe811d10a4 C:\WINDOWS\System32\win32u.dll+00004260 NtUserPeekMessage+00000020 [ 40] 0x00007ffe8414f2ed C:\WINDOWS\System32\USER32.dll+00127725 PeekMessageW+00000381 [ 41] 0x00007ffe8414f156 C:\WINDOWS\System32\USER32.dll+00127318 PeekMessageA+00000278 [ 42] 0x000000006aff94db C:\Program Files\MATLAB\R2013b\bin\win64\uiw.dll+00234715 UIW_SetCurrentDialog+00000731 [ 43] 0x000000006b021632 C:\Program Files\MATLAB\R2013b\bin\win64\uiw.dll+00398898 ws_FreeSystemFont+00000482 [ 44] 0x000000006f156600 C:\Program Files\MATLAB\R2013b\bin\win64\libmwservices.dll+01009152 services::system_events::PpeDispatchHook::~PpeDispatchHook+00055552 [ 45] 0x000000006f156fc5 C:\Program Files\MATLAB\R2013b\bin\win64\libmwservices.dll+01011653 services::system_events::PpeDispatchHook::~PpeDispatchHook+00058053 [ 46] 0x000000006f157e10 C:\Program Files\MATLAB\R2013b\bin\win64\libmwservices.dll+01015312 services::system_events::PpeDispatchHook::~PpeDispatchHook+00061712 [ 47] 0x000000006f160596 C:\Program Files\MATLAB\R2013b\bin\win64\libmwservices.dll+01050006 sysq::removeProcessPendingEventsHook+00010998 [ 48] 0x000000006f16089a C:\Program Files\MATLAB\R2013b\bin\win64\libmwservices.dll+01050778 svWS_ProcessPendingEvents+00000138 [ 49] 0x000000006e4e552d C:\Program Files\MATLAB\R2013b\bin\win64\mcr.dll+00087341 mcr::runtime::setInterpreterThreadToCurrent+00033693 [ 50] 0x000000006e4e57fb C:\Program Files\MATLAB\R2013b\bin\win64\mcr.dll+00088059 mcr::runtime::setInterpreterThreadToCurrent+00034411 [ 51] 0x000000006e4d9545 C:\Program Files\MATLAB\R2013b\bin\win64\mcr.dll+00038213 mcrInstantiationError::operator=+00003221 [ 52] 0x000000006e4dc872 C:\Program Files\MATLAB\R2013b\bin\win64\mcr.dll+00051314 mcr_invoke_on_interpreter_thread+00001602 [ 53] 0x000000006e4e98e6 C:\Program Files\MATLAB\R2013b\bin\win64\mcr.dll+00104678 mcrDesktopMain+00000230 [ 54] 0x0000000140004f0b C:\Program Files\MATLAB\R2013b\bin\win64\MATLAB.exe+00020235 [ 55] 0x0000000140006a07 C:\Program Files\MATLAB\R2013b\bin\win64\MATLAB.exe+00027143 [ 56] 0x00007ffe838f2774 C:\WINDOWS\System32\KERNEL32.DLL+00075636 BaseThreadInitThunk+00000020 [ 57] 0x00007ffe84810d51 C:\WINDOWS\SYSTEM32\ntdll.dll+00462161 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. If this problem is reproducible, please submit a Service Request via: http://www.mathworks.com/support/contact_us/ A technical support engineer might contact you with further information. Thank you for your help.


Jan-Mathijs Schoffelen - 2017-11-30 16:36:46 +0100

I have never worked with matlab on windows 10, nor do I have a machine available to reproduce this, but this smells like an incompatibility issue between the operating system and the compiled mex-files. Do you have a way to re-compile the mex files on your windows machine?


Jan-Mathijs Schoffelen - 2018-01-26 09:52:53 +0100

.


Robert Oostenveld - 2019-08-10 12:37:29 +0200

This closes a whole series of bugs that have been resolved (either FIXED/WONTFIX/INVALID) for quite some time. If you disagree, please file a new issue on https://github.com/fieldtrip/fieldtrip/issues.