Crash in colorer(?)

[singalen]

trafficstars

far2l 2.6.0.beta.

Happened when the laptop went to sleep:

Thread 2 Crashed:
0   libsystem_kernel.dylib        	    0x7ff818d84196 __pthread_kill + 10
1   libsystem_pthread.dylib       	    0x7ff818dbbee6 pthread_kill + 263
2   libsystem_c.dylib             	    0x7ff818ce2b45 abort + 123
3   far2l                         	       0x1089b2358 CustomPanic + 504
4   far2l                         	       0x108b97727 Panic(char const*, ...) + 455
5   far2l                         	       0x108b2e1ec SafeMMap::sSigaction(int, __siginfo*, void*) + 460
6   libsystem_platform.dylib      	    0x7ff818de95ed _sigtramp + 29
7   libsystem_malloc.dylib        	    0x7ff818c06960 nanov2_malloc_zero_on_alloc + 618
8   colorer.far-plug-wide         	       0x10e5305b5 FarEditor::editorEvent(int, void*) + 2133
9   colorer.far-plug-wide         	       0x10e536d02 FarEditorSet::editorEvent(int, void*) + 1074
10  far2l                         	       0x108b09b31 PluginW::ProcessEditorEvent(int, void*) + 49
11  far2l                         	       0x108b002a7 PluginManager::ProcessEditorEvent(int, void*) + 119
12  far2l                         	       0x108a27a30 FileEditor::DisplayObject() + 96
13  far2l                         	       0x108acebd7 GetInputRecord(_INPUT_RECORD*, bool, bool, bool) + 2071
14  far2l                         	       0x108a6d137 Manager::ProcessMainLoop() + 167
15  far2l                         	       0x108a6e408 Manager::EnterMainLoop() + 40
16  far2l                         	       0x108a6ab37 FarAppMain(int, char**) + 7895
17  far2l_gui.so                  	       0x108ef2af0 WinPortAppThread::Entry() + 32
18  libwx_baseu-3.2.0.2.1.dylib   	       0x1094a7b95 wxThreadInternal::PthreadStart(wxThread*) + 1751
19  libsystem_pthread.dylib       	    0x7ff818dbc1d3 _pthread_start + 125
20  libsystem_pthread.dylib       	    0x7ff818db7bd3 thread_start + 15

[unxed]

For newcomers: how do you get such detailed call stack?

[ctapmex]

is the error repeated again when going to sleep? on the other hand, if there was no memory at the time of waking up, then what could the plugin do? there might not even be a memory error to show.

[singalen]

how do you get such detailed call stack?

MacOS shows a window with crash dump before sending it to Apple, as a part of standard error reporting.

is the error repeated again when going to sleep?

Not, so far it was a one-off case.

on the other hand, if there was no memory at the time of waking up, then what could the plugin do? there might not even be a memory error to show.

I seriously doubt that there was no memory. The rest of the system ran fine, and I have Activity Monitor running all the time to make sure no process is hogging my RAM/CPU.

There are other possible scenarios, like corrupted data in malloc() argument, so it requested 0xFFFFFFFFFFFFFFF0 bytes of memory.

[ctapmex]

malloc is not used in the code. there is a realloc, but it checks the response after the call. It's hard to say anything on the stack yet

[elfmz]

malloc likely came from new that used alot there. Are you using prebuild binary or built custom one? In second case please share your colorer.far-plug-wide

[singalen]

Prebuilt.