1 2 Previous Next 25 Replies Latest reply on Sep 10, 2011 2:47 AM by eric

    FM11 PRO Unstable, Crashes often.

    JohnWesterman

      Summary

      FM11 PRO Unstable, Crashes often.

      Product

      FileMaker Pro

      Version

      11.02.22

      Operating system version

      OS X 10.6.5

      Description of the issue

      Trying to evaluate the software but I can't seem to keep it running. This has to be something I'm doing as I don't see anything related to the problem I'm experiencing. I experience in two different computers. I have downloaded the dmg file and verified the MD5 using two different browsers. I have unininstalled and re-installed to no avail.

      MD5 (fmp_trial_fm_11.0.2.220.dmg) = 274b9272e44f7be56afd06cc135224de

      Steps to reproduce the problem

      All I have to do is create a new database, enter some data, control-click a field to try to change the properties and the program becomes unstable.

      Expected result

      Not to crash.

      Actual result

      Crashes

      Exact text of any error message(s) that appear

      Spinner and then:

      What does all this mean? Can you tell why my installation is crashing?

      Process:         FileMaker Pro [27724]
      Path:            /Applications/FileMaker Pro 11/FileMaker Pro.app/Contents/MacOS/FileMaker Pro
      Identifier:      com.filemaker.client.pro
      Version:         11.0.2 (11.0.2)
      Code Type:       X86 (Native)
      Parent Process:  launchd [435]

      Date/Time:       2010-12-24 01:58:23.651 -0500
      OS Version:      Mac OS X 10.6.5 (10H574)
      Report Version:  6

      Interval Since Last Report:          1116839 sec
      Crashes Since Last Report:           3
      Per-App Interval Since Last Report:  2546 sec
      Per-App Crashes Since Last Report:   3
      Anonymous UUID:                      6D2BC3D3-2961-4C90-ADA6-DCABAE89F8C2

      Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
      Exception Codes: KERN_INVALID_ADDRESS at 0x00000000cccd0020
      Crashed Thread:  0  Dispatch queue: com.apple.main-thread

      Application Specific Information:
      objc_msgSend() selector name: release


      Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
      0   libobjc.A.dylib                    0x98549ed7 objc_msgSend + 23
      1   com.apple.Foundation               0x947eba18 __delayedPerformCleanup + 59
      2   com.apple.CoreFoundation           0x97609222 CFRunLoopTimerInvalidate + 786
      3   com.apple.CoreFoundation           0x975c3e8b __CFRunLoopRun + 9003
      4   com.apple.CoreFoundation           0x975c1464 CFRunLoopRunSpecific + 452
      5   com.apple.CoreFoundation           0x975c1291 CFRunLoopRunInMode + 97
      6   com.apple.HIToolbox                0x9176af9c RunCurrentEventLoopInMode + 392
      7   com.apple.HIToolbox                0x9176ad51 ReceiveNextEventCommon + 354
      8   com.apple.HIToolbox                0x9176abd6 BlockUntilNextEventMatchingListInMode + 81
      9   com.apple.AppKit                   0x961d478d _DPSNextEvent + 847
      10  com.apple.AppKit                   0x961d3fce -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156
      11  com.apple.AppKit                   0x96196247 -[NSApplication run] + 821
      12  com.filemaker.client.pro           0x0002c04d CMacApp_Main + 413
      13  com.filemaker.client.pro           0x00160a83 main + 51
      14  com.filemaker.client.pro           0x000034c6 start + 54

      Thread 1:  Dispatch queue: com.apple.libdispatch-manager
      0   libSystem.B.dylib                  0x904c9982 kevent + 10
      1   libSystem.B.dylib                  0x904ca09c _dispatch_mgr_invoke + 215
      2   libSystem.B.dylib                  0x904c9559 _dispatch_queue_invoke + 163
      3   libSystem.B.dylib                  0x904c92fe _dispatch_worker_thread2 + 240
      4   libSystem.B.dylib                  0x904c8d81 _pthread_wqthread + 390
      5   libSystem.B.dylib                  0x904c8bc6 start_wqthread + 30

      Thread 2:
      0   libSystem.B.dylib                  0x904d10a6 __semwait_signal + 10
      1   libSystem.B.dylib                  0x904fcee5 nanosleep$UNIX2003 + 188
      2   ...filemaker.support.framework     0x027ad7ac Draco::Thread::Sleep(unsigned long) + 172
      3   ...filemaker.support.framework     0x027adbac Draco::TimerCheckThread::Main() + 252
      4   ...filemaker.support.framework     0x027a9ece Draco::Thread::RunThread() + 46
      5   ...filemaker.support.framework     0x027ab198 Draco::Thread::ThreadUnixProc(void*) + 72
      6   libSystem.B.dylib                  0x904d085d _pthread_start + 345
      7   libSystem.B.dylib                  0x904d06e2 thread_start + 34

      Thread 3:
      0   libSystem.B.dylib                  0x904d10a6 __semwait_signal + 10
      1   libSystem.B.dylib                  0x904d0d62 _pthread_cond_wait + 1191
      2   libSystem.B.dylib                  0x904d29f8 pthread_cond_wait$UNIX2003 + 73
      3   ...filemaker.support.framework     0x027ac2df Draco::Semaphore::P(Draco::Thread*) + 159
      4   ...filemaker.support.framework     0x027acef5 Draco::MsgQ::GetMsg() + 69
      5   ...ilemaker.dbengine.framework     0x02927de0 Draco::HBEngine::HBEngineThread::Main() + 128
      6   ...filemaker.support.framework     0x027a9ece Draco::Thread::RunThread() + 46
      7   ...filemaker.support.framework     0x027ab198 Draco::Thread::ThreadUnixProc(void*) + 72
      8   libSystem.B.dylib                  0x904d085d _pthread_start + 345
      9   libSystem.B.dylib                  0x904d06e2 thread_start + 34

      Thread 4:
      0   libSystem.B.dylib                  0x904d10a6 __semwait_signal + 10
      1   libSystem.B.dylib                  0x904d0d62 _pthread_cond_wait + 1191
      2   libSystem.B.dylib                  0x904d29f8 pthread_cond_wait$UNIX2003 + 73
      3   ...filemaker.support.framework     0x027ac2df Draco::Semaphore::P(Draco::Thread*) + 159
      4   ...filemaker.support.framework     0x027acef5 Draco::MsgQ::GetMsg() + 69
      5   ...ilemaker.dbengine.framework     0x02a27ac7 Draco::DBEngineThread::Main() + 135
      6   ...filemaker.support.framework     0x027a9ece Draco::Thread::RunThread() + 46
      7   ...filemaker.support.framework     0x027ab198 Draco::Thread::ThreadUnixProc(void*) + 72
      8   libSystem.B.dylib                  0x904d085d _pthread_start + 345
      9   libSystem.B.dylib                  0x904d06e2 thread_start + 34

      Thread 5:
      0   libSystem.B.dylib                  0x904d10a6 __semwait_signal + 10
      1   libSystem.B.dylib                  0x904d0d62 _pthread_cond_wait + 1191
      2   libSystem.B.dylib                  0x904d29f8 pthread_cond_wait$UNIX2003 + 73
      3   ...filemaker.support.framework     0x027ac2df Draco::Semaphore::P(Draco::Thread*) + 159
      4   ...filemaker.support.framework     0x027acef5 Draco::MsgQ::GetMsg() + 69
      5   ...ilemaker.dbengine.framework     0x02a91358 Draco::DBLockContinueThread::Main() + 648
      6   ...filemaker.support.framework     0x027a9ece Draco::Thread::RunThread() + 46
      7   ...filemaker.support.framework     0x027ab198 Draco::Thread::ThreadUnixProc(void*) + 72
      8   libSystem.B.dylib                  0x904d085d _pthread_start + 345
      9   libSystem.B.dylib                  0x904d06e2 thread_start + 34

      Thread 6:  com.apple.CFSocket.private
      0   libSystem.B.dylib                  0x904c20c6 select$DARWIN_EXTSN + 10
      1   com.apple.CoreFoundation           0x97601c83 __CFSocketManager + 1091
      2   libSystem.B.dylib                  0x904d085d _pthread_start + 345
      3   libSystem.B.dylib                  0x904d06e2 thread_start + 34

      Thread 7:
      0   libSystem.B.dylib                  0x904c8a12 __workq_kernreturn + 10
      1   libSystem.B.dylib                  0x904c8fa8 _pthread_wqthread + 941
      2   libSystem.B.dylib                  0x904c8bc6 start_wqthread + 30

      Thread 0 crashed with X86 Thread State (32-bit):
        eax: 0x06e4491a  ebx: 0x963fd7d8  ecx: 0x96962f40  edx: 0xcccd0000
        edi: 0x06ec14b0  esi: 0x96962f40  ebp: 0xbfffe568  esp: 0xbfffe528
         ss: 0x00000023  efl: 0x00210202  eip: 0x98549ed7   cs: 0x0000001b
         ds: 0x00000023   es: 0x00000023   fs: 0x00000000   gs: 0x0000000f
        cr2: 0xcccd0020

      Binary Images:
          0x1000 -   0x7f8ff6 +com.filemaker.client.pro 11.0.2 (11.0.2) <89A415FD-0A0C-6494-D03A-AD21D3DD4C52> /Applications/FileMaker Pro 11/FileMaker Pro.app/Contents/MacOS/FileMaker Pro
        0xbfd000 -   0xcfcfff +DL81ACE 81.0.6 (compatibility 81.0.1) /Applications/FileMaker Pro 11/FileMaker Pro.app/Contents/Frameworks/DL81ACE.framework/Versions/A/DL81ACE
        0xd48000 -  0x1278fe7 +DL81AGM 81.0.27 (compatibility 81.0.1) /Applications/FileMaker Pro 11/FileMaker Pro.app/Contents/Frameworks/DL81AGM.framework/Versions/A/DL81AGM
      0x15ab000 -  0x15e9fe7 +DL81ARE 81.0.4 (compatibility 81.0.1) /Applications/FileMaker Pro 11/FileMaker Pro.app/Contents/Frameworks/DL81ARE.framework/Versions/A/DL81ARE
      0x1617000 -  0x163efdd +DL81AXE8SharedExpat 81.0.5 (compatibility 81.0.1) <28CEAC8D-44A3-430B-B57E-7F59C8F8D5B0> /Applications/FileMaker Pro 11/FileMaker Pro.app/Contents/Frameworks/DL81AXE8SharedExpat.framework/Versions/A/DL81AXE8SharedExpat
      0x1653000 -  0x166cfff +DL81BIB 81.0.4 (compatibility 81.0.1) /Applications/FileMaker Pro 11/FileMaker Pro.app/Contents/Frameworks/DL81BIB.framework/Versions/A/DL81BIB
      0x168c000 -  0x16abfff +DL81BIBUtils 81.0.4 (compatibility 81.0.1) /Applications/FileMaker Pro 11/FileMaker Pro.app/Contents/Frameworks/DL81BIBUtils.framework/Versions/A/DL81BIBUtils
      0x16d0000 -  0x1988fd7 +DL81CoolType 81.0.4 (compatibility 81.0.1) /Applications/FileMaker Pro 11/FileMaker Pro.app/Contents/Frameworks/DL81CoolType.framework/Versions/A/DL81CoolType
      0x1b40000 -  0x1bf7fea +com.datalogics.DL81JP2K 44.0.221 (44.0.221) /Applications/FileMaker Pro 11/FileMaker Pro.app/Contents/Frameworks/DL81JP2K.framework/Versions/A/DL81JP2K
      0x1c27000 -  0x1c8dfc0 +DL81XMP 81.0.7 (compatibility 81.0.1) <7072A484-6C56-4D55-813A-307F34D55D65> /Applications/FileMaker Pro 11/FileMaker Pro.app/Contents/Frameworks/DL81XMP.framework/Versions/A/DL81XMP
      0x1cb4000 -  0x22d2ff7 +DL81PDFL 81.0.74 (compatibility 81.0.1) /Applications/FileMaker Pro 11/FileMaker Pro.app/Contents/Frameworks/DL81PDFL.framework/Versions/A/DL81PDFL
      0x25f3000 -  0x26f0fef +DLI_PDFL81 81.0.21 (compatibility 81.0.16) /Applications/FileMaker Pro 11/FileMaker Pro.app/Contents/Frameworks/DLI_PDFL81.framework/Versions/A/DLI_PDFL81
      0x2724000 -  0x288bff9 +com.filemaker.support.framework FileMaker Support version 11.0.2 (11.0.2) <52FCF9A3-6239-6758-5CB9-5583C27CADA3> /Applications/FileMaker Pro 11/FileMaker Pro.app/Contents/Frameworks/Support.framework/Versions/A/Support
      0x291f000 -  0x2f55fe6 +com.filemaker.dbengine.framework FileMaker DBEngine version 11.0.2 (11.0.2) <6C585AAD-591E-0EBF-F4BD-140C5F22F003> /Applications/FileMaker Pro 11/FileMaker Pro.app/Contents/Frameworks/DBEngine.framework/Versions/A/DBEngine
      0x3210000 -  0x3488fef +com.filemaker.fmengine.framework FileMaker FMEngine version 11.0.2 (11.0.2) <435EE7D2-73B1-C6CB-0DF3-3BA842EBD776> /Applications/FileMaker Pro 11/FileMaker Pro.app/Contents/Frameworks/FMEngine.framework/Versions/A/FMEngine
      0x3602000 -  0x37aafff +com.filemaker.omniorb4.framework OmniORB4 version 4.1.3 (4.1.3) /Applications/FileMaker Pro 11/FileMaker Pro.app/Contents/Frameworks/OmniORB4.framework/Versions/A/OmniORB4
      0x3982000 -  0x3abefe3 +com.filemaker.openssl.framework OpenSSL version 0.9.8i (0.9.8i) /Applications/FileMaker Pro 11/FileMaker Pro.app/Contents/Frameworks/OpenSSL.framework/Versions/A/OpenSSL
      0x3b26000 -  0x3b97ff7 +libetpan.13.dylib 15.2.0 (compatibility 15.0.0) <0B8A1B39-2883-CF87-9629-B2220E5FA991> /Applications/FileMaker Pro 11/FileMaker Pro.app/Contents/Frameworks/libetpan.13.dylib
      0x3bbc000 -  0x3e4effc +libxerces-c-3.0.dylib ??? (???) <4852B70F-946F-0C8F-66D7-C7A02CFAD83F> /Applications/FileMaker Pro 11/FileMaker Pro.app/Contents/Frameworks/libxerces-c-3.0.dylib
      0x3fdd000 -  0x401dff7  libiodbc.2.dylib 4.18.0 (compatibility 4.0.0) <11BC09C6-77FC-189E-F5C4-9517CCAA35AC> /usr/lib/libiodbc.2.dylib
      0x4063000 -  0x4064ff7  com.apple.textencoding.unicode 2.3 (2.3) <78A61FD5-70EE-19EA-48D4-3481C640B70D> /System/Library/TextEncodings/Unicode Encodings.bundle/Contents/MacOS/Unicode Encodings

      Workaround

      I have not found any.

        • 1. Re: FM11 PRO Unstable, Crashes often.
          JohnWesterman

          In working with support I have learned there is some type of an issue. Older software (10.0.3.303) does not experience the same issue on my workstation. Seems like there is some incompatibility between Mac OSX 10.6.5 and FM Pro 11.

          • 2. Re: FM11 PRO Unstable, Crashes often.
            philmodjunk

            Snow Leopard had a number of issues with fonts and font suitcases that affected a number of applications, especially FileMaker. Most users have been able to resolve this by removing bad fonts/suitcases and installing the latest updates from Apple. You can search this forum for more info and you may also want to investigate this issue on Apple's site.

            • 3. Re: FM11 PRO Unstable, Crashes often.
              JohnWesterman

              Phil,

              I read about this issue on this forum but I have no idea even how to check to see if my fonts or font suitcase is good or bad. I don't even know what a font suitcase. As a user of the system I just want to build the database. I didn't know I was going to have to be a font expert! Two things I am not good at: fonts and printing. Both either have to work or I am somewhat out of my realm of influence. None the less, I'll poke around and see if I can figure out what a bad font suitcase looks like.

              John

              • 4. Re: FM11 PRO Unstable, Crashes often.
                JohnWesterman

                Phil,

                I have reviewed all of my fonts, removed duplicates, verified that I don't have any PS type 1 fonts installed and I still have this issue. I then "verified" my fonts using Font Book and it believes that all my fonts are valid and usable. I am beginning to think that fonts are not my problem.

                10.x works fine on this machine. I'm thinking that this is a 10.6.5 incompatibility and I'm reasonably certain, because I am having this problem on 3 different machines I own, that the problem is more wide-spread that I originally thought initially.

                I don't know what the problem is, but I know it can be reproduced easily. In the console logs I see the following message:

                1/2/11 01:23:58 FileMaker Pro[961] *** Assertion failure in -[FMDocWindowCocoa findToolbarView], /Volumes/Builds/BuildFMP11AppMac/FMPro11Mac_396/Client/FMPro/MacOS/../src/OSDocWindow/FMDocWindowControllerCocoa.m:5661/2/11 01:23:58 FileMaker Pro[961] An NSToolbarView* named '_toolbarView' no longer exists on NSToolbar

                This happens every time I right click a field that gives me the initial problem.

                When I researched the use of this program on the FM web site it was clear about what was supported (10.6.*). There is no exclusion for 10.6.5.

                I have my leopard disc in hand and I think I'm going to restore one of my machines back to a base configuration then apply 10.6.4 update, reinstall FMPA11 and see if I have the same issue. If not, I am going to apply the 10.6.5 update and see if the issu still exists. I'll report what I find.

                John

                • 5. Re: FM11 PRO Unstable, Crashes often.
                  philmodjunk

                  The problem with your conclusion is that many other folks are using FileMaker 11 with Snow Leopard and are not experiencing any of these issues.

                  This happens every time I right click a field that gives me the initial problem.

                  Does this statement mean that you get a crash only with specific fields on not with others? If so, see any common denominators? What happens if you change the specified font for this field and use Replace field contents with the function TextFormatRemove to strip all text styling from the text inside this field for all records in your table?

                  ...right click...

                  Out of curiosity, last time I used a mac, it only had one button. Are you using some kind of third party app that enables right clicks to work as shift clicks or does the current release of the Mac OS support two button mice?

                  • 6. Re: FM11 PRO Unstable, Crashes often.
                    JohnWesterman

                    Phil,

                    You are a funny guy. Of course you can right click, with a pressure sensitive mighty mouse. See image:

                    http://gallery.me.com/jwwmac#100298

                    I wish I was making that up or that you could brand me a Windows user. Sure, you can control-click too and I do that as well. But I occasionally right-click. Yes, I do. Because I can. And I even think it's a Steve Jobs approved action.

                    Curious how all this dialog helps me use this very expensive software successfully.

                    To further answer your question, you can, a-hem, control-click any field and it has the exact same issue. This software is currently unusable on my machines, all 4 of them.

                    John

                    • 7. Re: FM11 PRO Unstable, Crashes often.
                      philmodjunk

                      No humor intended. I'm not suggesting that you can't or shouldn't right click on a Mac. I'm just looking for any possible causes that explain why so many other users have been able to resolve their issues with Snow Leopard and you can't.

                      If you use a standard Mac mouse and shift click, do you get the same crash issue? If not, maybe it's the  mouse and FileMaker could then use that info to investigate this more effectively. If you still get the same crash when you don't right-click, then it's something else.

                      • 8. Re: FM11 PRO Unstable, Crashes often.
                        JohnWesterman

                        Phil,

                        I do get the exact same behavior. I can control-click any field and the only thing that happens is that the menu appears very briefly then goes away (split second) and the following shows up in the console logs:

                        1/2/11 01:23:58 FileMaker Pro[961] *** Assertion failure in -[FMDocWindowCocoa findToolbarView], /Volumes/Builds/BuildFMP11AppMac/FMPro11Mac_396/Client/FMPro/MacOS/../src/OSDocWindow/FMDocWindowControllerCocoa.m:5661/2/11 01:23:58 FileMaker Pro[961] An NSToolbarView* named '_toolbarView' no longer exists on NSToolbar

                        If you do this control clicking enough or try to force yourself into the interface (clicking every possible option) the program will eventually crash with crash logs as indicated in the initial complaint of this thread. I have several of these if they would be helpful.

                        The behavior will eventually show up if you get into the designing tools and try to change the field layout, fonts, etc. Essentially anything other than entering data into the database will cause failure and abnormal termination of the application.

                        This does not happen in FM10. I learned that FM11 is built from the ground up with Cocoa. The error logs indicate a Cocoa issue. I'm no programmer but this would seem like something to do with the setup and interface with Cocoa to me. But I wouldn't know where to start troubleshooting that.

                        John

                        • 9. Re: FM11 PRO Unstable, Crashes often.
                          TSGal

                          John Westerman:

                          Thank you for your posts (and thank you PhilModJunk for your troubleshooting help), and I apologize for the late reply.

                          I have FileMaker Pro 11 running on Snow Leopard from every incarnation of 10.6.1 to the current 10.6.6 without any problem.  For clarification purposes, did you install the same copy of FileMaker Pro on four different machines?  This may account for the same error occurring.  Have each computer download the latest version, 11.0v3, from our web site.  After installation, try again.

                          Are all four machines purposefully installed exactly the same?  Or, does each person install their own OS?

                          Have you removing all fonts and installing just the standard fonts supplied by Apple?

                          If you already found a solution, please post so others can also benefit.

                          TSGal
                          FileMaker, Inc.

                          • 10. Re: FM11 PRO Unstable, Crashes often.
                            RayNovitske

                            I just downloaded FMPro 11.0v2 test version. Selecting custom color for text crashes every time. Standard colors work fine. Using 10.6.2 on MacBook Pro Intel Core 2 Duo. I would hate to spend money on a software product that doesn't fully work.

                            I found a post in these discussion about this happening with the Advanced version, but no others. The Apple custom color selectors have been working fine with my other programs since Macbook purchase in January 2010. Any suggestions?

                            • 11. Re: FM11 PRO Unstable, Crashes often.
                              TSGal

                              Ray Novitske:

                              The closest configuration I could find to yours is as follows:

                              MacBook Pro Intel Core Duo, 1.83 GHz

                              Mac OS X 10.6.6

                              FileMaker Pro 11.0v2 trial version.

                              I created a new database file, one text field, entered data into the field, highlighted the data, pulled down the Format menu, selected Text Color -> Other Color..., pulled the color wheel slider to the middle, clicked on a shade of purple color, and clicked OK.  No crash.  I tried several different settings in case I got lucky selecting one of the preset colors.  Still, no crash.

                              Do you have access to another computer?  If so, does it work correctly?

                              Any other information you can provide may be helpful.

                              TSGal
                              FileMaker, Inc.

                              • 12. Re: FM11 PRO Unstable, Crashes often.
                                RayNovitske

                                Using 2.53 GHz Macbook Pro

                                It must be the OS - 10.6.2 which I am using, and 10.6.6 you used. Maybe the update corrects some issues.

                                I will try updating the OS this weekend to see if that solves the problem. Thanks for your quick response.

                                • 13. Re: FM11 PRO Unstable, Crashes often.
                                  RickWhitelaw

                                  Hi,

                                  I really don't have a meaningful contribution to offer, other than the fact that I'm running OS X 10.6.6 and FMPA 11.03 and am not experiencing any problems (font or other) described in this thread. 

                                  RW

                                  • 14. Re: FM11 PRO Unstable, Crashes often.
                                    JohnWesterman

                                    Wesley,

                                    It's been a while, but I was finally able to get a disk, image it with Mac OSX 10.5.8 and install FMPA 11.0v2. It seems to work perfectly on that computer now.

                                    So, where do I go from here? I would like to say that I created this problem by doing something funky to my computer(s). But I didn't. Each computer is independent and one not created by anything from the other. The only common thing I can find is that FMPA doesn't run on any of them running Snow Leopard.

                                    I have software I purchased in December that I still can not use and I don't know why. It has something to do with Cocoa but I don't know what. Do I open a ticket with Apple? Do I open another thread with support?

                                    I have thought about getting the "Genius" dudes/dudettes to help me but when I went to the store last time and described my problem all I heard was crickets and got a blank stare as if I was speaking a language not understood. So a little leary there.

                                    Open for suggestions. Everyone else seems to get it to work but I can't seem to make it happen. Very odd.

                                    John

                                    1 2 Previous Next