EXC_BAD_ACCESS (SIGSEGV)

Discussion in 'OS X El Capitan (10.11)' started by jazzwineman, May 22, 2016.

  1. jazzwineman macrumors newbie

    jazzwineman

    Joined:
    May 22, 2016
    #1
    I am not a programmer and so some of this makes little sense to me, however as I read the log, it seems to indicate read/write memory problems (cache or cache size-perhaps). I just upgraded someone from Mavericks to El Capitan and this occurs on an intermittent basis and sometimes will go for days without happening and then wallop, 3 or 4 times in a row. Could someone be kind enough to give a cursory glance at this and let me know what they think the problem is? There were a number of Binary Images- however the forum kept telling me that it had invalid characters in the message and would not post.





    Thanks for your time and help.





    Process: Runtime [3137]

    Path: /Applications/MentalNt32/MentalNt32.app/Contents/MacOS/Runtime

    Identifier: com.filemaker.client.runtime.MentalNt32

    Version: 11.0.1 (11.0.1)

    Code Type: X86 (Native)

    Parent Process: ??? [1]

    Responsible: Runtime [3137]

    User ID: 501



    Date/Time: 2016-05-17 16:02:10.375 -0500

    OS Version: Mac OS X 10.11.4 (15E65)

    Report Version: 11

    Anonymous UUID: E02D64F8-AF87-C361-6011-AA1AC8BF9FD0



    Sleep/Wake UUID: 65F9A5FA-D794-41D7-B94F-717A0A098B9C



    Time Awake Since Boot: 28000 seconds

    Time Since Wake: 16000 seconds



    System Integrity Protection: disabled



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



    Exception Type: EXC_BAD_ACCESS (SIGSEGV)

    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000020

    Exception Note: EXC_CORPSE_NOTIFY



    VM Regions Near 0x20:

    -->

    __TEXT 0000000000001000-00000000006a0000 [ 6780K] r-x/rwx SM=COW /Applications/MentalNt32/MentalNt32.app/Contents/MacOS/Runtime



    Application Specific Information:

    objc_msgSend() selector name: release





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

    0 libobjc.A.dylib 0x998accaf objc_msgSend + 31

    1 com.apple.CoreFoundation 0x951de69f _CFAutoreleasePoolPop + 47

    2 com.apple.Foundation 0x9068efe8 -[NSAutoreleasePool drain] + 122

    3 com.apple.AppKit 0x926cdc3e -[NSApplication run] + 946

    4 com.filemaker.client.runtime.MentalNt32 0x0033f7ad CMacApp_Main + 413

    5 com.filemaker.client.runtime.MentalNt32 0x000cfdc3 main + 51

    6 com.filemaker.client.runtime.MentalNt32 0x00003146 start + 54



    Thread 1:: Dispatch queue: com.apple.libdispatch-manager

    0 libsystem_kernel.dylib 0x9d5437fa kevent_qos + 10

    1 libdispatch.dylib 0x911237ea _dispatch_mgr_invoke + 234

    2 libdispatch.dylib 0x911233be _dispatch_mgr_thread + 52



    Thread 2:

    0 libsystem_kernel.dylib 0x9d5427ce __semwait_signal + 10

    1 libsystem_c.dylib 0x9e5e98cd nanosleep$UNIX2003 + 218

    2 com.filemaker.support.framework 0x012199dc Draco::Thread::Sleep(unsigned long) + 172

    3 com.filemaker.support.framework 0x01219ddc Draco::TimerCheckThread::Main() + 252

    4 com.filemaker.support.framework 0x012160fe Draco::Thread::RunThread() + 46

    5 com.filemaker.support.framework 0x012173c8 Draco::Thread::ThreadUnixProc(void*) + 72

    6 libsystem_pthread.dylib 0x94f63780 _pthread_body + 138

    7 libsystem_pthread.dylib 0x94f636f6 _pthread_start + 155

    8 libsystem_pthread.dylib 0x94f60f7a thread_start + 34



    Thread 3:

    0 libsystem_kernel.dylib 0x9d5423ea __psynch_cvwait + 10

    1 libsystem_pthread.dylib 0x94f64538 _pthread_cond_wait + 757

    2 libsystem_pthread.dylib 0x94f66276 pthread_cond_wait$UNIX2003 + 71

    3 com.filemaker.support.framework 0x0121850f Draco::Semaphore::p(Draco::Thread*) + 159

    4 com.filemaker.support.framework 0x01219125 Draco::MsgQ::GetMsg() + 69

    5 com.filemaker.dbengine.framework 0x01394b90 Draco::HBEngine::HBEngineThread::Main() + 128

    6 com.filemaker.support.framework 0x012160fe Draco::Thread::RunThread() + 46

    7 com.filemaker.support.framework 0x012173c8 Draco::Thread::ThreadUnixProc(void*) + 72

    8 libsystem_pthread.dylib 0x94f63780 _pthread_body + 138

    9 libsystem_pthread.dylib 0x94f636f6 _pthread_start + 155

    10 libsystem_pthread.dylib 0x94f60f7a thread_start + 34



    Thread 4:

    0 libsystem_kernel.dylib 0x9d5423ea __psynch_cvwait + 10

    1 libsystem_pthread.dylib 0x94f64538 _pthread_cond_wait + 757

    2 libsystem_pthread.dylib 0x94f66276 pthread_cond_wait$UNIX2003 + 71

    3 com.filemaker.support.framework 0x0121850f Draco::Semaphore::p(Draco::Thread*) + 159

    4 com.filemaker.support.framework 0x01219125 Draco::MsgQ::GetMsg() + 69

    5 com.filemaker.dbengine.framework 0x0148cfc7 Draco::DBEngineThread::Main() + 135

    6 com.filemaker.support.framework 0x012160fe Draco::Thread::RunThread() + 46

    7 com.filemaker.support.framework 0x012173c8 Draco::Thread::ThreadUnixProc(void*) + 72

    8 libsystem_pthread.dylib 0x94f63780 _pthread_body + 138

    9 libsystem_pthread.dylib 0x94f636f6 _pthread_start + 155

    10 libsystem_pthread.dylib 0x94f60f7a thread_start + 34



    Thread 5:

    0 libsystem_kernel.dylib 0x9d5423ea __psynch_cvwait + 10

    1 libsystem_pthread.dylib 0x94f64538 _pthread_cond_wait + 757

    2 libsystem_pthread.dylib 0x94f66276 pthread_cond_wait$UNIX2003 + 71

    3 com.filemaker.support.framework 0x0121850f Draco::Semaphore::p(Draco::Thread*) + 159

    4 com.filemaker.support.framework 0x01219125 Draco::MsgQ::GetMsg() + 69

    5 com.filemaker.dbengine.framework 0x014f63a8 Draco::DBLockContinueThread::Main() + 648

    6 com.filemaker.support.framework 0x012160fe Draco::Thread::RunThread() + 46

    7 com.filemaker.support.framework 0x012173c8 Draco::Thread::ThreadUnixProc(void*) + 72

    8 libsystem_pthread.dylib 0x94f63780 _pthread_body + 138

    9 libsystem_pthread.dylib 0x94f636f6 _pthread_start + 155

    10 libsystem_pthread.dylib 0x94f60f7a thread_start + 34



    Thread 6:: com.apple.NSEventThread

    0 libsystem_kernel.dylib 0x9d53b49a mach_msg_trap + 10

    1 libsystem_kernel.dylib 0x9d53a884 mach_msg + 68

    2 com.apple.CoreFoundation 0x95221dc6 __CFRunLoopServiceMachPort + 214

    3 com.apple.CoreFoundation 0x952211d1 __CFRunLoopRun + 1521

    4 com.apple.CoreFoundation 0x95220976 CFRunLoopRunSpecific + 390

    5 com.apple.CoreFoundation 0x952207db CFRunLoopRunInMode + 123

    6 com.apple.AppKit 0x92842f76 _NSEventThread + 291

    7 libsystem_pthread.dylib 0x94f63780 _pthread_body + 138

    8 libsystem_pthread.dylib 0x94f636f6 _pthread_start + 155

    9 libsystem_pthread.dylib 0x94f60f7a thread_start + 34



    Thread 7:: CVDisplayLink

    0 libsystem_kernel.dylib 0x9d5423ea __psynch_cvwait + 10

    1 libsystem_pthread.dylib 0x94f64538 _pthread_cond_wait + 757

    2 libsystem_pthread.dylib 0x94f66276 pthread_cond_wait$UNIX2003 + 71

    3 com.apple.CoreVideo 0x97eaca0d CVDisplayLink::runIOThread() + 931

    4 com.apple.CoreVideo 0x97eac2bb startIOThread(void*) + 159

    5 libsystem_pthread.dylib 0x94f63780 _pthread_body + 138

    6 libsystem_pthread.dylib 0x94f636f6 _pthread_start + 155

    7 libsystem_pthread.dylib 0x94f60f7a thread_start + 34



    Thread 8:

    0 libsystem_kernel.dylib 0x9d542d5e __workq_kernreturn + 10

    1 libsystem_pthread.dylib 0x94f6334b _pthread_wqthread + 1289

    2 libsystem_pthread.dylib 0x94f60f56 start_wqthread + 34



    Thread 9:

    0 libsystem_kernel.dylib 0x9d542d5e __workq_kernreturn + 10

    1 libsystem_pthread.dylib 0x94f6334b _pthread_wqthread + 1289

    2 libsystem_pthread.dylib 0x94f60f56 start_wqthread + 34



    Thread 10:

    0 libsystem_kernel.dylib 0x9d542d5e __workq_kernreturn + 10

    1 libsystem_pthread.dylib 0x94f6334b _pthread_wqthread + 1289

    2 libsystem_pthread.dylib 0x94f60f56 start_wqthread + 34



    Thread 0 crashed with X86 Thread State (32-bit):

    eax: 0x15830500 ebx: 0x02838010 ecx: 0x998c8b12 edx: 0x00000000

    edi: 0x998ac93f esi: 0x02838000 ebp: 0xbffff878 esp: 0xbffff638

    ss: 0x00000023 efl: 0x00210206 eip: 0x998accaf cs: 0x0000001b

    ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f

    cr2: 0x00000020



    Logical CPU: 1

    Error Code: 0x00000004

    Trap Number: 14







    External Modification Summary:

    Calls made by other processes targeting this process:

    task_for_pid: 5

    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: 11185

    thread_create: 0

    thread_set_state: 0



    VM Region Summary:

    ReadOnly portion of Libraries: Total=300.6M resident=0K(0%) swapped_out_or_unallocated=300.6M(100%)

    Writable regions: Total=197.6M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=197.6M(100%)



    VIRTUAL REGION

    REGION TYPE SIZE COUNT (non-coalesced)

    =========== ======= =======

    ATS (font support) 33.0M 6

    ATS (font support) (reserved) 4K 2 reserved VM address space (unallocated)

    1. Accelerate.framework 256K 3
    Activity Tracing 2048K 2

    CG backing stores 12.9M 8

    CG image 68K 10

    CG shared images 400K 11

    CoreAnimation 324K 16

    CoreUI image data 1716K 18

    CoreUI image file 192K 4

    Foundation 24K 3

    IOKit 15.5M 2

    Image IO 240K 17

    Kernel Alloc Once 4K 2

    MALLOC 111.4M 55

    MALLOC guard page 64K 14

    Memory Tag 242 12K 2

    Memory Tag 249 156K 2

    OpenCL 40K 6

    OpenGL GLSL 128K 3

    Process Corpse Info 2048K 2

    Stack 12.6M 12

    Stack Guard 56.0M 12

    VM_ALLOCATE 272K 31

    WebKit Malloc 4120K 4

    __DATA 28.2M 312

    __GLSLBUILTINS 2588K 2

    __IMAGE 528K 2

    __IMPORT 172K 11

    __LINKEDIT 62.5M 54

    __OBJC 5272K 113

    __TEXT 238.1M 313

    __UNICODE 552K 2

    mapped file 254.1M 102

    shared memory 16.4M 10

    =========== ======= =======

    TOTAL 861.4M 1133

    TOTAL, minus reserved VM space 861.4M 1133



    Model: MacBookPro5,3, BootROM MBP53.00AC.B03, 2 processors, Intel Core 2 Duo, 3.06 GHz, 8 GB, SMC 1.48f2

    Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MB

    Graphics: NVIDIA GeForce 9600M GT, NVIDIA GeForce 9600M GT, PCIe, 512 MB

    Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1067 MHz, 0x8319, 0x4E4947553538504942202020202020202020

    Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1067 MHz, 0x8319, 0x4E4947553538504942202020202020202020

    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.106.98.100.24)

    Bluetooth: Version 4.4.4f4 17685, 3 services, 19 devices, 1 incoming serial ports

    Network Service: Wi-Fi, AirPort, en1

    Serial ATA Device: CT500BX100SSD1, 500.11 GB

    Serial ATA Device: MATSHITADVD-R UJ-868

    USB Device: USB 2.0 Bus

    USB Device: Built-in iSight

    USB Device: USB 2.0 Bus

    USB Device: Card Reader

    USB Device: Ultra

    USB Device: USB Bus

    USB Device: BRCM2046 Hub

    USB Device: Bluetooth USB Host Controller

    USB Device: USB Bus

    USB Device: Apple Internal Keyboard / Trackpad
     
  2. grahamperrin macrumors 601

    grahamperrin

    Joined:
    Jun 8, 2007
    #2
  3. jazzwineman thread starter macrumors newbie

    jazzwineman

    Joined:
    May 22, 2016
    #3
    I do indeed appreciate your response. But managing some 15,000 computers, that would normally be the first thing I would do and since they do not exist and have not for 4 years ago, I have to go to alternative resources. I do not mean this in a bad way, as you are trying to help,, but you are stating the obvious. Yes it does say made by Filemaker.

    Thank yoo anyway. I am just trying to get help in reading what is there and help a doctor client/friend that is having intermittent problems.
     
  4. leman macrumors 604

    Joined:
    Oct 14, 2008
    #4
    Well, that's a bug in the app. What else do you want us to say? The error means that the app is accessing a non-existent memory location. Most likely one of those things that work on one OS X and stop working on the next one because the dev didn't bother to read the docs. Not much you can do without having access to the source code or contact to the developer.
     
  5. jazzwineman thread starter macrumors newbie

    jazzwineman

    Joined:
    May 22, 2016
    #5
    Thank you. I thought it was a dealing with memory read and write errors. It worked in Mavericks but not El Capitan. Strange, I would think it would happen every time, however it is intermittent. There are not many adjustable options in the program. I did adjust cache, which is 64 mb by default to 128mb and made a check on saving the cache every 10 minutes vs when the program is idle. I do not know if either will have an affect. I did tell the client that without source code, anyone would be helpless.
     
  6. leman macrumors 604

    Joined:
    Oct 14, 2008
    #6
    I would guess it's a memory leak or something along those lines. Why it didn't trigger in Mavericks - could have literally hundreds of reasons. I'm afraid that without the support of the original developer it's a dead end.
     
  7. NoBoMac macrumors 6502a

    Joined:
    Jul 1, 2014
    #7
    What leman said.

    Memory leaks, NULL pointer, invalid pointer, accessing memory freed by the program, improperly allocating memory, buffer overflows, etc etc.

    And not that strange. Change in environment can expose the bug(s) in the code. Had a similar thing happen once for me: in house code ran as expected for over a year, updated the operating environment, exposed a NULL pointer bug in the code.

    Per error dump, it appears to be an invalid pointer error:

    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000020

    Most likely the app, not anything is OS X. If it were OS related, would be seeing more of these and from more apps.
     
  8. jazzwineman thread starter macrumors newbie

    jazzwineman

    Joined:
    May 22, 2016
    #8
    Thanks all for your help. It does confirm my thoughts and the client probably needs to get a new program and not try and go back to older OS issues that eventually won't be supported or other items may not work in at some point.
    Thanks again.

    Cheers!

    Tom
     
  9. NoBoMac macrumors 6502a

    Joined:
    Jul 1, 2014
    #9
    No reason not to go back to previous. If there is a TimeMachine backup and or clone, should be able to get things back to the way they were. And then leave the machine as is, until a plan is in place to determine which apps are incompatible, need upgrading, etc. and tested in some dual-boot mode.

    Other than security updates, probably no compelling features in El Cap where the machine needs to be upgraded.
     
  10. grahamperrin macrumors 601

    grahamperrin

    Joined:
    Jun 8, 2007
    #10
    If your client wishes to continue with both the old application and El Capitan, then would he or she consider running Mavericks or less in (say) a VirtualBoxVM for that application alone?
     
  11. jazzwineman thread starter macrumors newbie

    jazzwineman

    Joined:
    May 22, 2016
    #11
    We run vm fusion for a specific windows program. Which vm box would you recommend for running mavericks? My only problem and perhaps this makes no difference, but the install program that he had downloaded originally (a compressed file) is corrupted. I am wondering if this might transfer in a fine way to a new install, although have a time machine backup as it originally was laid out and I assume that could go into a virtual cox as well. Thoughts and thanks big time

    Tom
     
  12. grahamperrin macrumors 601

    grahamperrin

    Joined:
    Jun 8, 2007
    #12
    In recent years I have not tried anything other than VirtualBox. My main gripe is that some Command- key combinations don't work as expected. Like, Command-Q with my thumb on the left Command key is not interpreted as a quit of the app that's in front in the guest; it's interpreted as a quit of the guest.
     
  13. NoBoMac macrumors 6502a

    Joined:
    Jul 1, 2014
    #13
    Appears Fusion 6.0-8.0 can handle Mavericks.

    As for an installer, if client "purchased their copy legally (ie. downloaded from App Store via their Apple ID), should still be in the list under "Purchased" tab. Mine is still there, and shows as downloadable.

    As for anything else Fusion related, haven't used it since upgrading to Yosemite: currently using VirtualBox and only with Windows.
     
  14. jazzwineman thread starter macrumors newbie

    jazzwineman

    Joined:
    May 22, 2016
    #14
    Can I take the time machine backup of Mavericks and load on virtual box. I have not rhad a chance to read, but curious if it can be done.
    --- Post Merged, May 23, 2016 ---
    I do not have the installer for the Mental Notes Program- am not worried about the VM Fusion. Will virtual box take a time machine backup and load that as an operating system?
     
  15. grahamperrin macrumors 601

    grahamperrin

    Joined:
    Jun 8, 2007
    #15
    I doubt it.

    Something like this might work:
    1. restore from the Time Machine backup to a physical drive in an enclosure with a USB connection
    2. in a VirtualBoxVM guest, have two virtual disks
    3. install any version of OS X to one of the two
    4. in the host machine, unmount but do not eject the OS X startup volume that is on the physical drive
    5. in the VirtualBoxVM guest, connect to the physical drive
    6. in the guest, clone the content of the physical drive to the second virtual disk
    … something like that. A long time since I went through the routine, a little forethought was required to have what *was* the secondary virtual disk become a primary device for boot purposes in the guest. If that makes sense – I'm sleepy now, past midnight and maybe not explaining it properly!
     

Share This Page