Re: Maxbulk crashes systematically after about 23000 email s
hello I'm back after several months I did not use MBM and the issue discussed in this thread is still there and, again, occurs systematically. After your advice, I could finally copy and save the crash logs.
Searching for "crash" word in the crash log, I found it occurs in the log start lines as follows:
Process: MaxBulk Mailer [38628]
Path: /Applications/MaxBulk Mailer/MaxBulk Mailer.app/Contents/MacOS/MaxBulk Mailer
Identifier: com.maxprog.maxbulkmailer
Version: 8.5 (8.5.0.3.0)
Code Type: X86 (Native)
Parent Process: ??? [1]
Responsible: MaxBulk Mailer [38628]
User ID: 501
Date/Time: 2015-09-23 01:49:40.760 +0200
OS Version: Mac OS X 10.10.5 (14F27)
Report Version: 11
Anonymous UUID: 8A8E63EA-DE68-FC88-1324-45A49C96A7FF
Sleep/Wake UUID: 4E3D0D50-6EB5-411E-8F8B-81052E2F3014
Time Awake Since Boot: 560000 seconds
Time Since Wake: 12000 seconds
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
abort() called
terminating with uncaught exception of type std::bad_alloc: std::bad_alloc
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x98e8869a __pthread_kill + 10
1 libsystem_pthread.dylib 0x90ea3634 pthread_kill + 101
2 libsystem_c.dylib 0x9a1a9dee abort + 156
3 libc++abi.dylib 0x9310c2f9 abort_message + 169
4 libc++abi.dylib 0x9312f483 default_terminate_handler() + 272
5 libc++abi.dylib 0x9312cac0 std::__terminate(void (*)()) + 14
6 libc++abi.dylib 0x9312c4db __cxa_throw + 122
7 libc++abi.dylib 0x9312cd04 operator new(unsigned long) + 100
8 rbframework.dylib 0x0158fe70 0x1582000 + 56944
9 rbframework.dylib 0x01590573 0x1582000 + 58739
10 rbframework.dylib 0x01590027 0x1582000 + 57383
11 rbframework.dylib 0x015a19a5 0x1582000 + 129445
12 rbframework.dylib 0x015b2288 SocketWrite + 88
13 com.maxprog.maxbulkmailer 0x000597ea 0x1000 + 362474
14 RBSSL.xojo_plugin_0.dylib 0x049677fa 0x4963000 + 18426
15 RBSSL.xojo_plugin_0.dylib 0x0496783b 0x4963000 + 18491
16 RBSSL.xojo_plugin_0.dylib 0x04966f11 0x4963000 + 16145
17 RBSSL.xojo_plugin_0.dylib 0x04966977 0x4963000 + 14711
18 RBSSL.xojo_plugin_0.dylib 0x04966434 0x4963000 + 13364
19 RBSSL.xojo_plugin_0.dylib 0x04965220 0x4963000 + 8736
20 RBSSL.xojo_plugin_0.dylib 0x04965a35 0x4963000 + 10805
21 com.maxprog.maxbulkmailer 0x001bb848 0x1000 + 1812552
22 rbframework.dylib 0x016236a8 0x1582000 + 661160
23 rbframework.dylib 0x01592755 0x1582000 + 67413
24 rbframework.dylib 0x0160aa23 0x1582000 + 559651
25 com.maxprog.maxbulkmailer 0x0002dbc1 0x1000 + 183233
26 com.maxprog.maxbulkmailer 0x000c9b52 0x1000 + 822098
27 rbframework.dylib 0x0160a794 0x1582000 + 558996
28 rbframework.dylib 0x0160ab30 0x1582000 + 559920
29 rbframework.dylib 0x015d4f22 RuntimeRun + 50
30 com.maxprog.maxbulkmailer 0x0024512c 0x1000 + 2375980
31 com.maxprog.maxbulkmailer 0x000086fe 0x1000 + 30462
32 com.maxprog.maxbulkmailer 0x00002614 0x1000 + 5652
33 com.maxprog.maxbulkmailer 0x01451305 0x1000 + 21299973
34 com.maxprog.maxbulkmailer 0x0145125b 0x1000 + 21299803
Then it occurs in the crash log after about a hundred lines as follows:
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0xa0fc66d0 ecx: 0xbfffd26c edx: 0x00000000
edi: 0xa057e1d4 esi: 0x00000006 ebp: 0xbfffd288 esp: 0xbfffd26c
ss: 0x00000023 efl: 0x00000206 eip: 0x98e8869a cs: 0x0000000b
ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f
cr2: 0xa0fc4a00
Logical CPU: 0
Error Code: 0x00080148
Trap Number: 132
I compared two differente MBM crash logs and the lines here above are exactly the same (each value).
I confirm that crash seem to ALWAYS occur after about 22000 emails sent.
System general info: MacBook core2duo (aluminum late 2008), 8Gb RAM, OS X 10.10.5
(side note: I'm not facing any problem with any other app, so I don't think is a OS X issue)
I hope this time I could finally provide exhaustive information for detecting the issue. I saved two full crash logs but they're long to be posted here so I can send by email it if you need. Regards.