Help interpreting Apple hard crash report

  1. 5 days ago

    Aaron H

    Feb 11 Pre-Release Testers Germany

    Reading this crash report, it looks to me like the Xojo RealSQLDatabase object is running out of memory at 2.6GB trying to perform a query. If this is correct, then the question is: WHY? 64-bit apps are supposed to have unlimited memory access. Thanks for your help.
    ====================

    Process: VSSP [503]
    Path:
    /Volumes/VOLUME/*/VSSP-06Feb2019.app/Contents/MacOS/VSSP
    Identifier: com.zentralzone.VSSP
    Version: 1.0.4 (1.0.4.0.0)
    Code Type: X86-64 (Native)
    Parent Process: ??? [1]
    Responsible: VSSP [503]
    User ID: 501

    Date/Time: 2019-02-09 20:45:09.633 +0000
    OS Version: Mac OS X 10.11.6 (15G31)
    Report Version: 11
    Anonymous UUID: 6FBED662-BD9D-FF12-FB9F-14A7FF4D7A8F

    Sleep/Wake UUID: EFCD5EE3-DABE-4AA7-8C5E-BC59C0E30B83

    Time Awake Since Boot: 100000 seconds
    Time Since Wake: 67000 seconds

    System Integrity Protection: enabled

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

    Exception Type: EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x00000001a3cae000
    Exception Note: EXC_CORPSE_NOTIFY

    VM Regions Near 0x1a3cae000:
    MALLOC_LARGE_REUSABLE 000000019cd74000-00000001a3cae000 [111.2M]
    rw-/rwx SM=PRV
    -->
    STACK GUARD 0000700000083000-0000700000084000 [ 4K]
    ---/rwx SM=NUL stack guard for thread 1

    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0 REALSQLDatabase.dylib 0x0000000106e2dfb1 0x106e29000 +
    20401
    1 REALSQLDatabase.dylib 0x0000000106e2ed62 0x106e29000 +
    23906
    2 REALSQLDatabase.dylib 0x0000000106e2f387 0x106e29000 +
    25479
    3 com.zentralzone.VSSP 0x00000001021ba746
    RealSQLDatabase.SQLSelect%o<RecordSet>%o<RealSQLDatabase>sb + 86
    4 com.zentralzone.VSSP 0x0000000102905e96
    VSSPDatabase.SQLSelect_do%o<RecordSet>%o<VSSPDatabase>s + 86
    5 com.zentralzone.VSSP 0x0000000102ae7d8c
    DatabaseWindow.DatabaseWindow.DB_LoadCurrentSpan%%o<DatabaseWindow.DatabaseW
    indow> + 220
    6 com.zentralzone.VSSP 0x0000000102aa753b
    DatabaseWindow.DatabaseWindow.Timer_CalcProperties_Action%%o<DatabaseWindow.
    DatabaseWindow>o<Timer> + 59
    7 com.xojo.XojoFramework 0x000000010359eded 0x10333e000 +
    2493933
    8 com.apple.CoreFoundation 0x00007fff83cbbb94
    __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
    9 com.apple.CoreFoundation 0x00007fff83cbb823
    __CFRunLoopDoTimer + 1075
    10 com.apple.CoreFoundation 0x00007fff83cbb37a
    __CFRunLoopDoTimers + 298
    11 com.apple.CoreFoundation 0x00007fff83cb2871 __CFRunLoopRun +
    1841
    12 com.apple.CoreFoundation 0x00007fff83cb1ed8
    CFRunLoopRunSpecific + 296
    13 com.apple.HIToolbox 0x00007fff8d7da935
    RunCurrentEventLoopInMode + 235
    14 com.apple.HIToolbox 0x00007fff8d7da76f
    ReceiveNextEventCommon + 432
    15 com.apple.HIToolbox 0x00007fff8d7da5af
    _BlockUntilNextEventMatchingListInModeWithFilter + 71
    16 com.apple.AppKit 0x00007fff851c1df6 _DPSNextEvent +
    1067
    17 com.apple.AppKit 0x00007fff851c1226 -[NSApplication
    _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454
    18 com.xojo.XojoFramework 0x00000001034138a9 0x10333e000 +
    874665
    19 com.xojo.XojoFramework 0x00000001034138ed 0x10333e000 +
    874733
    20 com.zentralzone.VSSP 0x000000010213ff45
    Application._CallFunctionWithExceptionHandling%%o<Application>p + 181
    21 com.xojo.XojoFramework 0x0000000103596c07
    CallFunctionWithExceptionHandling(void (*)()) + 262
    22 com.xojo.XojoFramework 0x0000000103413856 0x10333e000 +
    874582
    23 com.apple.AppKit 0x00007fff851b5d80 -[NSApplication
    run] + 682
    24 com.xojo.XojoFramework 0x0000000103594f79 RuntimeRun + 42
    25 com.zentralzone.VSSP 0x00000001021d83d3
    REALbasic._RuntimeRun + 19
    26 com.zentralzone.VSSP 0x00000001031597d6 _Main + 326
    27 com.zentralzone.VSSP 0x00000001031449a3 main + 19
    28 libdyld.dylib 0x00007fff917c55ad start + 1

    [ ... omitted other info because this would be otherwise too long to post ... ]

    External Modification Summary:
    Calls made by other processes targeting this process:
    task_for_pid: 21325
    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: 4183830
    thread_create: 0
    thread_set_state: 0

    VM Region Summary:
    ReadOnly portion of Libraries: Total=319.2M resident=0K(0%)
    swapped_out_or_unallocated=319.2M(100%)
    Writable regions: Total=2.1G written=0K(0%) resident=0K(0%)
    swapped_out=0K(0%) unallocated=2.1G(100%)

    VIRTUAL REGION
    REGION TYPE SIZE COUNT (non-coalesced)
    =========== ======= =======
    Accelerate.framework 256K 3
    Activity Tracing 2048K 2
    CG backing stores 24.4M 6
    CG image 568K 45
    CG shared images 400K 11
    CoreAnimation 704K 42
    CoreUI image data 5336K 32
    CoreUI image file 192K 4
    Dispatch continuations 16.0M 2
    Foundation 24K 3
    Kernel Alloc Once 8K 3
    MALLOC 2.1G 124
    MALLOC guard page 32K 7
    Memory Tag 242 12K 2
    Memory Tag 251 12K 2
    OpenCL 8K 2
    Process Corpse Info 2048K 2
    STACK GUARD 56.0M 4
    Stack 8784K 4
    VM_ALLOCATE 84K 13
    __DATA 31.2M 293
    __IMAGE 528K 2
    __LINKEDIT 95.1M 22
    __TEXT 224.1M 299
    __UNICODE 552K 2
    __XOJO 8K 2
    mapped file 87.6M 38
    shared memory 16.3M 8
    =========== ======= =======
    TOTAL 2.6G 951

    Model: MacBookPro11,3, BootROM MBP112.0138.B17, 4 processors, Intel Core i7,
    2.5 GHz, 16 GB, SMC 2.19f12
    Graphics: Intel Iris Pro, Intel Iris Pro, Built-In
    Graphics: NVIDIA GeForce GT 750M, NVIDIA GeForce GT 750M, PCIe, 2048 MB
    Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD,
    0x484D54343147533641465238412D50422020
    Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD,
    0x484D54343147533641465238412D50422020
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x134),
    Broadcom BCM43xx 1.0 (7.21.95.175.1a6)
    Bluetooth: Version 4.4.6f1 17910, 3 services, 18 devices, 1 incoming serial
    ports
    PCI Card: pci1b21,612, AHCI Controller, Thunderbolt@194,0,0
    Serial ATA Device: APPLE SSD SM0512F, 500.28 GB
    Serial ATA Device: HGST HUS726040ALE614, 4 TB
    USB Device: USB 3.0 Bus
    USB Device: Apple Internal Keyboard / Trackpad
    USB Device: BRCM20702 Hub
    USB Device: Bluetooth USB Host Controller
    Thunderbolt Bus: MacBook Pro, Apple Inc., 17.1
    Thunderbolt Device: G-DRIVE Thunderbolt 3 USB 3.1, G-Technology, 1, 24.1

  2. Dave S

    Feb 11 San Diego, California USA

    What version of Xojo? RealSQLDatabase was deprecated in favor of SQLiteDatabase years ago
    Also, a query may be returning 2.6g, but the interim workspace could be much larger

  3. Aaron H

    Feb 11 Pre-Release Testers Germany

    @Dave S SQLiteDatabase

    Hi Dave. I suppose that may be the problem! This is the latest version of Xojo. The app is a behemoth from almost a decade ago, revived for 64-bits.

  4. Dave S

    Feb 11 San Diego, California USA

    you should just be able to swap the keywords and move on.... not saying it will solve the problem, but at least you will be insured to be using the most up to date version of SQLite supported by Xojo

  5. Aaron H

    Feb 11 Pre-Release Testers Germany
    Edited 5 days ago

    Thanks, I've just done that. Recompiled and sending to the client now for testing.

    I'm a little bothered that Xojo didn't warn me that RealSQLDatabase is deprecated. That would have saved us some trouble here.

    I suppose probably it did tell me and I just missed it. Anyway thanks for the help!

  6. Bob K

    Feb 11 Pre-Release Testers, Xojo Pro Kansas City

    @Aaron H I'm a little bothered that Xojo didn't warn me that RealSQLDatabase is deprecated.

    Did you do a Check Project? Deprecations are shown there.

    Deprecated should not generate a compiler error because it's still there - it's really just a warning. The warnings shown in the Check Project will show you deprecated items as well as other things you might want to check.

  7. 4 days ago

    Aaron H

    Feb 11 Pre-Release Testers Germany

    @Bob K Did you do a Check Project? Deprecations are shown there.

    I thought I did a couple of years ago when I was asked to update this project for 64-bit. I guess I just missed it.

  8. Bob K

    Feb 11 Pre-Release Testers, Xojo Pro Kansas City

    REALSQLDatabase has been deprecated for longer than just a couple of years. You might want to bump the frequency of running check project. :)

or Sign Up to reply!