I have never understood the crash reports on macOS, so I have no idea how to interpret my problem. I have a webapp that has been compiling and running fine for many years. Now it is crashing shortly after starting up. This happens both in debug mode and standalone. In both case, I have found the crash report in the Console app, and it informs a EXC_BAD_ACCESS error on the same thread always (number 4). Other than that, I have no idea how to understand the report.
Upon startup my app begins to read an sqlite database that the app maintains, so that it can continue operation as finished the last time. It can read in several thousand SQL records into objects in memory. About 80% of the way the app crashes.
Please guide me on how to understand the report in order to track the problem, and even better, how to fix this problem.
Xojo 2019R3.1
macOS 10.15.5
RAM: 16GB
select the text of the crash report and paste it into a post
that may give otheres here enough info to provide clues about what is wrong
Yeah, I wanted to avoid pasting all that text, but I guess there is no avoiding it
That is strange… I am trying to paste here a copy of the crash report. It does get to show within the text box, but upon hitting the “Post a Reply”, nothing happens. If I write this text, the message does get posted, but not the copy/paste from the Crash Report.
Process: eValuar.debug [2059]
Path: /Users/USER/*/eValuar.debug
Identifier: eValuar.debug
Version: 0
Code Type: X86-64 (Native)
Parent Process: Xojo [1097]
Responsible: Xojo [1097]
User ID: 503
Date/Time: 2020-07-15 15:40:18.242 -0500
OS Version: Mac OS X 10.15.5 (19F101)
Report Version: 12
Anonymous UUID: 679AF4E0-739A-92E0-2855-2B95F5A7E703
Time Awake Since Boot: 9200 seconds
System Integrity Protection: enabled
Crashed Thread: 3
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000700008d36008
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [2059]
VM Regions Near 0x700008d36008:
Stack 0000700008cb4000-0000700008d36000 [ 520K] rw-/rwx SM=COW thread 3
–>
STACK GUARD 0000700008ebf000-0000700008ec0000 [ 4K] —/rwx SM=NUL stack guard for thread 4
Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff6fb5b882 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff6fc20425 _pthread_cond_wait + 698
2 rbframework.dylib 0x000000010b28bacc xojo::ConditionVariable::Wait(xojo::UniqueLock&) + 12
3 rbframework.dylib 0x000000010b296a26 0x10b0c7000 + 1899046
4 rbframework.dylib 0x000000010b2949bf 0x10b0c7000 + 1890751
5 eValuar.debug 0x0000000109d86c1b ConsoleApplication.DoEvents%%oi8 + 11
6 eValuar.debug 0x0000000109e647e0 WebApplication.Event_Run%i8%oA1s + 20592
7 rbframework.dylib 0x000000010b281053 CallConsoleApplicationRunEventHelper() + 358
8 eValuar.debug 0x0000000109d86e05 ConsoleApplication._CallFunctionWithExceptionHandling%%op + 181
9 rbframework.dylib 0x000000010b36682a CallFunctionWithExceptionHandling(void (*)()) + 138
10 rbframework.dylib 0x000000010b2fa5e9 RuntimeRun + 54
11 eValuar.debug 0x0000000109fb30d3 REALbasic._RuntimeRun + 19
12 eValuar.debug 0x000000010acaa59e _Main + 846 (/#main:82)
13 eValuar.debug 0x000000010aca8cd3 main + 19
14 libdyld.dylib 0x00007fff6fa17cc9 start + 1
Thread 1:
0 libsystem_pthread.dylib 0x00007fff6fc1bb68 start_wqthread + 0
Thread 2:: SessionShutDownThread
0 libsystem_kernel.dylib 0x00007fff6fb5b882 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff6fc20457 _pthread_cond_wait + 748
2 rbframework.dylib 0x000000010b28bb6a xojo::ConditionVariable::WaitFor(xojo::UniqueLock&, std::__1::chrono::duration<long long, std::__1::ratio<1l, 1000l> >) + 106
3 rbframework.dylib 0x000000010b295631 SleepToSystem(long) + 141
4 rbframework.dylib 0x000000010b2966f9 0x10b0c7000 + 1898233
5 rbframework.dylib 0x000000010b29499e 0x10b0c7000 + 1890718
6 eValuar.debug 0x0000000109d8c16b Thread.Sleep%%oi8b + 11
7 eValuar.debug 0x0000000109e8302c _SessionShutdownThread.Event_Run%%o<_SessionShutdownThread> + 444
8 rbframework.dylib 0x000000010b295dbb 0x10b0c7000 + 1895867
9 rbframework.dylib 0x000000010b28b899 0x10b0c7000 + 1853593
10 libsystem_pthread.dylib 0x00007fff6fc20109 _pthread_start + 148
11 libsystem_pthread.dylib 0x00007fff6fc1bb8b thread_start + 15
Thread 3 Crashed:
0 libsystem_pthread.dylib 0x00007fff6fc1dfe5 _pthread_tsd_cleanup + 440
1 libsystem_pthread.dylib 0x00007fff6fc20512 _pthread_exit + 70
2 libsystem_pthread.dylib 0x00007fff6fc1dddd _pthread_wqthread_exit + 77
3 libsystem_pthread.dylib 0x00007fff6fc1cafc _pthread_wqthread + 481
4 libsystem_pthread.dylib 0x00007fff6fc1bb77 start_wqthread + 15
There is a lot more text, but this forum does not let me paste in all of it
Would someone need all the rest?
It would be easier if you saved the crash report to a file and provide a link… or file a bug report.
[quote=496611:@Jorge Duran-Ballen]There is a lot more text, but this forum does not let me paste in all of it
Would someone need all the rest?[/quote]
Its OK
There first piece says
and then you posted some of thread 3 (unless there is more specific to thread 3 ?)
That portion from Thread 3 Crashed: to whatever follows (usually separated buy some blank lines) is whats important to look into
hopefully that gives some extra clues
Thread 3 crashed with X86 Thread State (64-bit):
rax: 0x0000000000007000 rbx: 0x00000000000003e4 rcx: 0x0000000000000030 rdx: 0x0000000000000000
rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000700008d33f60 rsp: 0x0000700008d33f10
r8: 0x0000000000064004 r9: 0xffffffffffffffff r10: 0x0000000000000003 r11: 0x0000000000000246
r12: 0x0000700008d34000 r13: 0x0000700008d34000 r14: 0x0000000000000000 r15: 0x00007fff96087e30
rip: 0x00007fff6fc1dfe5 rfl: 0x0000000000010206 cr2: 0x0000700008d36008
Logical CPU: 0
Error Code: 0x00000004 (no mapping for user data read)
Trap Number: 14
Binary Images:
0x109d3b000 - 0x10ad9fff7 +eValuar.debug (0) /Users/USER//eValuar.debug
0x10b0c7000 - 0x10b4b5fff +rbframework.dylib (0) <13605E96-8CD1-3E2E-BA4C-13E7D703DBE1> /Users/USER//rbframework.dylib
----- [very long list like above]
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 5142
thread_create: 0
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=598.6M resident=0K(0%) swapped_out_or_unallocated=598.6M(100%)
Writable regions: Total=115.7M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=115.7M(100%)
VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
Activity Tracing 256K 1
Dispatch continuations 8192K 1
Kernel Alloc Once 8K 1
MALLOC 95.9M 45
MALLOC guard page 16K 3
STACK GUARD 56.0M 5
Stack 10.0M 5
VM_ALLOCATE 4K 1
__DATA 26.7M 266
__DATA_CONST 24K 2
__FONT_DATA 4K 1
__LINKEDIT 398.8M 15
__OBJC_RO 32.2M 1
__OBJC_RW 1892K 2
__TEXT 199.7M 261
__UNICODE 564K 1
__XOJO 24K 1
mapped file 27.5M 3
shared memory 596K 9
=========== ======= =======
TOTAL 858.2M 624
There is also this part…
Thread 4:
0 libsystem_kernel.dylib 0x00007fff6fb5b882 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff6fc20425 _pthread_cond_wait + 698
2 rbframework.dylib 0x000000010b28bacc xojo::ConditionVariable::Wait(xojo::UniqueLock&) + 12
3 rbframework.dylib 0x000000010b296a26 0x10b0c7000 + 1899046
4 rbframework.dylib 0x000000010b2949bf 0x10b0c7000 + 1890751
5 eValuar.debug 0x0000000109d8c16b Thread.Sleep%%oi8b + 11
6 eValuar.debug 0x000000010a3128c0 Cenicienta.Event_Run%%o + 2160 (/Cenicienta:17)
7 rbframework.dylib 0x000000010b295dbb 0x10b0c7000 + 1895867
8 rbframework.dylib 0x000000010b28b899 0x10b0c7000 + 1853593
9 libsystem_pthread.dylib 0x00007fff6fc20109 _pthread_start + 148
10 libsystem_pthread.dylib 0x00007fff6fc1bb8b thread_start + 15
One of the most important part seems incomplete:
Thread 3 Crashed:
0 libsystem_pthread.dylib 0x00007fff6fc1dfe5 _pthread_tsd_cleanup + 440
1 libsystem_pthread.dylib 0x00007fff6fc20512 _pthread_exit + 70
2 libsystem_pthread.dylib 0x00007fff6fc1dddd _pthread_wqthread_exit + 77
…NEED THE REST TO SEE WHERE IT FAILS and have some clues
If you are afraid of publishing it here, open a PRIVATE FB Case, post the complete report, and only Xojo will see it.
Sorry Rick, what is a PRIVATE FB Case?
By the way, not afraid at all of publishing here. I actually tried to do that first, but this forum does not allow me to publish such a lengthy post, such as a crash report… So I had to break it up in pieces.
just copy the part from Thread 3 Crashed: down to Thread 4
THAT is the part we need to see
The text is so extensive that I cannot paste it here, so following Rick’s advice, please find it:
https://www.notion.so/Crash-Report-be9b912fc11b4f1b92875cecc6f123ed
And guys, thanks a million for your patience, and hopefully your advice !!
We use an App called “Feedback” to report bugs to Xojo. All users usually can see what we post there, except when we mark a case AS PRIVATE, so only Xojo can see the contents.
https://documentation.xojo.com/resources/reporting_bugs_and_making_feature_requests.html
“Visible To: Choose who can see your Feedback case. The default is typically “Everyone”, but if you have PRIVATE information in the case you can choose “Only me and Xojo”. For Beta cases, choose the appropriate Beta visibility.”
Seems your Work Queue thread crashed. Internal things occurred. A resource vanished before its time to be processed? Xojo needs to examine the case.
Hey Rick, the thread thing actually gives me a clue. However, it does seem to be a Xojo error, but maybe I can work around it. I’ll look into it.
It feels good to at least have a lead, because I was feeling really lost there. Thanks.