MWClient crash

Hi Chris,

In the latest nightly, using both a server-embedded-python script and a client bridge python script we saw a crash with the below backtrace:

This is somewhat high priority for us as if it recurs it will prevent us from using the latest nightly/python embed.
It only happened after an experiment had run quite a few trials, so I don’t know how we can deliver a test case. Ideas? Happy to talk about ways to help.

thanks,
Mark

Process: MWClient [829]
Path: /Applications/MWClient.app/Contents/MacOS/MWClient
Identifier: org.mworks-project.MWClient
Version: 0.8.dev-20170825 (da0d4a25)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: MWClient [829]
User ID: 502

Date/Time: 2017-08-31 11:20:15.166 -0400
OS Version: Mac OS X 10.12.6 (16G29)
Report Version: 12
Anonymous UUID: 423A48BD-7D2F-7720-89F8-36005FA478AB

Time Awake Since Boot: 3600 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]

VM Regions Near 0:

__TEXT 0000000106440000-000000010645d000 [ 116K] r-x/rwx SM=COW /Applications/MWClient.app/Contents/MacOS/MWClient

Application Specific Information:
Performing @selector(_outlineControlClicked:) from sender NSButton 0x610000341ad0

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_c.dylib 0x00007fff8cf08b52 strlen + 18
1 org.mworks-project.MWorksCocoa 0x0000000106a62877 -[MWCodec valueForVariable:] + 159
2 com.yourcompany.yourcocoabundle 0x000000010cc6b3bf -[MWVariablesWindowController setValue:forVariable:] + 244
3 com.yourcompany.yourcocoabundle 0x000000010cc69d41 -[MWVariablesWindowController controlTextDidEndEditing:] + 434
4 com.apple.CoreFoundation 0x00007fff7776845c CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER + 12
5 com.apple.CoreFoundation 0x00007fff7776835b _CFXRegistrationPost + 427
6 com.apple.CoreFoundation 0x00007fff777680c2 ___CFXNotificationPost_block_invoke + 50
7 com.apple.CoreFoundation 0x00007fff77725523 -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1827
8 com.apple.CoreFoundation 0x00007fff7772455c _CFXNotificationPost + 604
9 com.apple.Foundation 0x00007fff79149677 -[NSNotificationCenter postNotificationName:object:userInfo:] + 66
10 com.apple.AppKit 0x00007fff75417081 -[NSTextField textDidEndEditing:] + 329
11 com.apple.CoreFoundation 0x00007fff7776845c CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER + 12
12 com.apple.CoreFoundation 0x00007fff7776835b _CFXRegistrationPost + 427
13 com.apple.CoreFoundation 0x00007fff777680c2 ___CFXNotificationPost_block_invoke + 50

Hi Mark,

I think I found the problem. The fix will be in tonight’s nightly build. (FYI, the issue was in the variables window and was not related to any Python stuff.)

Chris

Excellent. It only happened to us once or twice but we are very happy to have a possible fix in.

Mark