SecuritySpy Crashes on App Startup….. see attached problem report. Hope this helps. Thanks…
  • Michael Mohel …. mmohel@icloud.com

    This is a partial report... did not know how to send the whole file to you.... If needed let me know how to send it.
    I would appreciate your help with this. Thanks again.



    Process: SecuritySpy [3091]
    Path: /Applications/SecuritySpy.app/Contents/MacOS/SecuritySpy
    Identifier: com.bensoftware.SecuritySpy
    Version: 4.1.6 (4.0)
    Code Type: X86-64 (Native)
    Parent Process: ??? [1]
    Responsible: SecuritySpy [3091]
    User ID: 501

    Date/Time: 2017-07-08 16:37:32.206 -0500
    OS Version: Mac OS X 10.13 (17A291m)
    Report Version: 12
    Anonymous UUID: 025E1A01-9E24-3F51-82CB-9C0C14CA683E


    Time Awake Since Boot: 3700 seconds

    System Integrity Protection: enabled

    Crashed Thread: 21

    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 00000001049aa000-0000000104c08000 [ 2424K] r-x/rwx SM=COW  [/Applications/SecuritySpy.app/Contents/MacOS/SecuritySpy]

    Application Specific Information:
    objc_msgSend() selector name: objectForKey:


    Thread 0:: Dispatch queue: com.apple.main-thread
    0 libsystem_kernel.dylib 0x00007fffd86defd2 mach_msg_trap + 10
    1 libsystem_kernel.dylib 0x00007fffd86de4ec mach_msg + 60
    2 com.apple.CoreFoundation 0x00007fffb125d935 __CFRunLoopServiceMachPort + 213
    3 com.apple.CoreFoundation 0x00007fffb125cd72 __CFRunLoopRun + 1506
    Michael Mohel …. mmohel@icloud.com



    Process: SecuritySpy [3091]
    Path: /Applications/SecuritySpy.app/Contents/MacOS/SecuritySpy
    Identifier: com.bensoftware.SecuritySpy
    Version: 4.1.6 (4.0)
    Code Type: X86-64 (Native)
    Parent Process: ??? [1]
    Responsible: SecuritySpy [3091]
    User ID: 501

    Date/Time: 2017-07-08 16:37:32.206 -0500
    OS Version: Mac OS X 10.13 (17A291m)
    Report Version: 12
    Anonymous UUID: 025E1A01-9E24-3F51-82CB-9C0C14CA683E


    Time Awake Since Boot: 3700 seconds

    System Integrity Protection: enabled

    Crashed Thread: 21

    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 00000001049aa000-0000000104c08000 [ 2424K] r-x/rwx SM=COW  [/Applications/SecuritySpy.app/Contents/MacOS/SecuritySpy]

    Application Specific Information:
    objc_msgSend() selector name: objectForKey:




    Model: Macmini6,2, BootROM MM61.0107.B01, 4 processors, Intel Core i7, 2.3 GHz, 16 GB, SMC 2.8f0
    Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In
    Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x859B, 0x435438473353313630424D2E4D3136464A44
    Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x859B, 0x435438473353313630424D2E4D3136464A44
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x10E), Broadcom BCM43xx 1.0 (7.21.190.10.1a1)
    Bluetooth: Version 6.0.0d47, 3 services, 27 devices, 1 incoming serial ports
    Network Service: Ethernet, Ethernet, en0
    Network Service: Wi-Fi, AirPort, en1
    Serial ATA Device: Samsung SSD 850 EVO 250GB, 250.06 GB
    Serial ATA Device: OWC Mercury EXTREME Pro SSD, 240.06 GB
    USB Device: USB 2.0 Bus
    USB Device: Hub
    USB Device: Hub
    USB Device: IR Receiver
    USB Device: BRCM20702 Hub
    USB Device: Bluetooth USB Host Controller
    USB Device: USB 2.0 Bus
    USB Device: Hub
    USB Device: USB 3.0 Bus
    USB Device: ASM1153E
    Thunderbolt Bus: Mac mini, Apple Inc., 23.4
  • This is a known problem with the current High Sierra Beta. It's a bug in the OS, and Apple is aware of it. I expect that they will fix it in an upcoming beta version. For now, if you need to use SecuritySpy, you will need to roll back to macOS 10.12.
  • Any news on if the latest beta released this week fixes the problem?
  • Upgraded to 10.13 Beta (17A306f) today.... still will not load.... same error message sent to Apple...
    Is there possibly a SecuritySpy Beta work around available that might work until the fix from Apple arrives that I might try?
    Thank you,

    Michael
  • Hi Michael,

    The crash is happening in a library called VideoToolbox that is used by SecuritySpy to decode incoming video data from the cameras. This crash is in Apple's code and there is nothing we can do about it unfortunately. I expect this will get fixed by Apple soon, but I don't know when. The only advice at the moment is to avoid High Sierra Beta.
  • Please could you both try the latest beta version of SecuritySpy (currently 4.1.7b8) as it has a fix related to video decompression in High Sierra that may resolve some of these problems. Please let me know if this works, or if problems remain (note that High Sierra is still in beta testing phase so there are likely to still be bugs in the system).
  • Same thing for me too Ben (2nd public beta), no joy with the beta, I just tried. We'll stay tuned...
  • Hi @fester - please upgrade to High Sierra Beta 3 (via the App Store on your Mac) and try the beta again (it's now on b9 so please obtain the new one from the SecuritySpy beta page). In our testing this now works fine with no crashes.
  • Update: High Sierra Beta 4 has just been released, and fixes another crashing problem related to video decompression. Please all update to this and try it with the latest SecuritySpy beta - this works in our testing.
  • Updated to latest High Sierra Beta today... Installed SecuritySpy 4.1.7b11.... working fine! Will see how it does and keep you posted.... Thank you Ben!

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!