App is crashing lately

Software Weather Display for Mac
1

Hi Brian,

The app has be crashing lately. Here is end details from the last crash. It has been happening every couple of weeks.

Thanks,

Sean

Process: weatherdisplay [425]
Path: /Applications/weatherdisplay.app/Contents/MacOS/weatherdisplay
Identifier: weatherdisplay
Version: 1.0 (1.0.0)
Code Type: X86 (Native)
Parent Process: ??? [1]
Responsible: weatherdisplay [425]
User ID: 501

Date/Time: 2019-04-02 18:51:57.476 -0700
OS Version: Mac OS X 10.13.6 (17G5019)
Report Version: 12
Anonymous UUID: 00493AE1-2897-9592-7AE2-23587460C58C

Time Awake Since Boot: 180000 seconds

System Integrity Protection: enabled

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

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00000000bf7fff24
Exception Note: EXC_CORPSE_NOTIFY

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

VM Regions Near 0xbf7fff24:
Stack 00000000b0b13000-00000000b0b94000 [ 516K] rw-/rwx SM=COW
→ Stack Guard 00000000bc000000-00000000bf800000 [ 56.0M] —/rwx SM=NUL
Stack 00000000bf800000-00000000bfff6000 [ 8152K] rw-/rwx SM=COW

Application Specific Information:
BUG IN CLIENT OF LIBDISPATCH: Semaphore object deallocated while in use

Thread 1:
0 libsystem_kernel.dylib 0xa73e4402 mach_msg_trap + 10
1 libsystem_kernel.dylib 0xa73e3a3f mach_msg + 47
2 weatherdisplay 0x00043af9 _dbk_fcall_wrapper + 82533
3 libsystem_pthread.dylib 0xa75a34d5 _pthread_body + 347
4 libsystem_pthread.dylib 0xa75a337a _pthread_start + 357
5 libsystem_pthread.dylib 0xa75a2a56 thread_start + 34

Thread 2:
0 libsystem_kernel.dylib 0xa73edd4e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0xa75a443c _pthread_cond_wait + 658
2 libsystem_pthread.dylib 0xa75a608c pthread_cond_wait$UNIX2003 + 51
3 libc++.1.dylib 0xa56a8669 std::__1::condition_variable::wait(std::__1::unique_lockstd::__1::mutex&) + 39
4 com.apple.JavaScriptCore 0x9644e32a void std::__1::condition_variable_any::wait<std::__1::unique_lockbmalloc::Mutex >(std::__1::unique_lockbmalloc::Mutex&) + 90
5 com.apple.JavaScriptCore 0x9644dfcc bmalloc::Scavenger::threadRunLoop() + 252
6 com.apple.JavaScriptCore 0x9644ddc1 bmalloc::Scavenger::threadEntryPoint(bmalloc::Scavenger*) + 17
7 com.apple.JavaScriptCore 0x9644e11f void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_deletestd::__1::__thread_struct >, void ()(bmalloc::Scavenger), bmalloc::Scavenger*> >(void*) + 47
8 libsystem_pthread.dylib 0xa75a34d5 _pthread_body + 347
9 libsystem_pthread.dylib 0xa75a337a _pthread_start + 357
10 libsystem_pthread.dylib 0xa75a2a56 thread_start + 34

Thread 3:: com.apple.NSEventThread
0 libsystem_kernel.dylib 0xa73e4402 mach_msg_trap + 10
1 libsystem_kernel.dylib 0xa73e3a3f mach_msg + 47
2 com.apple.CoreFoundation 0x9377f9b8 __CFRunLoopServiceMachPort + 296
3 com.apple.CoreFoundation 0x9377e9a6 __CFRunLoopRun + 2262
4 com.apple.CoreFoundation 0x9377dda1 CFRunLoopRunSpecific + 641
5 com.apple.CoreFoundation 0x9377db0a CFRunLoopRunInMode + 122
6 com.apple.AppKit 0x914aa580 _NSEventThread + 165
7 libsystem_pthread.dylib 0xa75a34d5 _pthread_body + 347
8 libsystem_pthread.dylib 0xa75a337a _pthread_start + 357
9 libsystem_pthread.dylib 0xa75a2a56 thread_start + 34

Thread 4:
0 libsystem_kernel.dylib 0xa73ee716 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0xa75a2e39 _pthread_wqthread + 992
2 libsystem_pthread.dylib 0xa75a2a32 start_wqthread + 34

Thread 5:
0 libsystem_kernel.dylib 0xa73ee716 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0xa75a2e64 _pthread_wqthread + 1035
2 libsystem_pthread.dylib 0xa75a2a32 start_wqthread + 34

Thread 6:
0 libsystem_kernel.dylib 0xa73ee716 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0xa75a3059 _pthread_wqthread + 1536
2 libsystem_pthread.dylib 0xa75a2a32 start_wqthread + 34

Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x00000000 ecx: 0x00000200 edx: 0xbf80039c
edi: 0x00032ee8 esi: 0xbf80039c ebp: 0xbf800338 esp: 0xbf7fff28
ss: 0x00000023 efl: 0x00210287 eip: 0x00030ef1 cs: 0x0000001b
ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f
cr2: 0xbf7fff24

Logical CPU: 2
Error Code: 0x00000006
Trap Number: 14

2

Downloading the lastest version that was update 4-4-19. I will let you know if it happens again.

Thanks

3

one solution is to restart it every few days maybe

4

Did you see this in the crash notes:

Application Specific Information:
BUG IN CLIENT OF LIBDISPATCH: Semaphore object deallocated while in use

5

Hi Brian,

I have been trying your suggest of restarting the app. The crashes are still happening.

They are at very specific time. 12am and 12pm. I am still getting the same error message of:

Application Specific Information:
BUG IN CLIENT OF LIBDISPATCH: Semaphore object deallocated while in use

Any suggestions?

Thanks,

Sean

6

a crash at a specific time is a big clue
12pm might be corrupted FWI data
(you could try deleting the fwi.inf and fwi2.inf data files)

7

Thx for the info.

I deleted the fwi.inf, I could not find the fwi2.inf file.

I will let you know how it goes.

8

Hi rigger3 - Did delete the file resolve your crashing issues? Mine is doing the same thing.

9

Yes, it seem to have worked. I have not experienced any crashes since deleting the files.

10

I did a lot of testing. I switched back to windows for a while until I had time to research the crashing issue. It seemed to crash anytime the program updated internet files. So, I checked and unchecked a bunch of options in the “Web Files Setup#1” tab. Once I unchecked the system from creating and uploading any of the dials, it stopped crash. The graphs do not seem to cause a problem, only dials.

Then I was curious as to if it was an issue creating GIFs. So, I toggled the option to create JPEG instead of GIF. The I turned back on some of the options to create dials. It DID NOT crash!!! Woohoo!

11

I spoke too soon. Right after I posted the message, it crashed. I checked the output files for the dials. The program created the rain dials, humidity, gust, directional, dew, barodial.jpg… then crashed. The offending file is called average dial.jpg. It was the last image created before the crash.

averagedial.jpg

12

ah, the option to create individual dials
I will test/check on that

13

Hi Brian, I’m a software developer myself, so I know developing a program this complex is difficult. You are doing a great job. I have found a few other annoying bugs in the MAC version build 315. Should I post these in the Bugs/Issues thread or in the Mac thread? I wish I knew enough about development on a MAC to help and test.

14

i have made some fixes for the individual dial images, latest update

15

Hi Brian,

I have tried Build 315 and it closes at 11 minutes past midnight each night. Here is the error message in the System Log

Jun 16 00:11:09 PJL-2 com.apple.xpc.launchd[1] (com.apple.xpc.launchd.oneshot.0x100085c7.weatherdisplay[94377]): Service exited due to SIGSEGV | sent by exc handler[94377]
.

I also reviewed all settings and did not find any specific setting that requires actions such as file creation or file upload that is set to 11 minutes past midnight. Any thoughts on what could cause the crash? Previously using Build 307 and that works ok so I went back to that.

Thanks

16

that is when the av/ext is updated
so you could try turning that off as a test (in the upload times in the ftp/internet setup)

17

Hi Brian, yes that seems to be the cause. I unchecked the option for the ave/ext as you suggested and Build 315 kept going through the night.

18

if you could email me your settings files and your data file (month62019.inf) and logfile 62019lg.txt
then I can test here

I have not made any changes to the av/ext routine for a while though

19

have tested here with your settings and your logfile and data file
and turned on to update the av/ext
it did not crash at 12:11am

email me though also your climatedata.html webfile

20

that file causes the crash
investigating