BC for MAC crashed after closing MacBook build 17451

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Juergen
    Visitor
    • Jan 2014
    • 6

    BC for MAC crashed after closing MacBook build 17451

    I have received the following message an close the program with cmd q now.

    message:

    05/01/14 14:36:38
    UUID: 97DFC629-6380-378C-B48D-641659851B26
    Beyond Compare Version 4.0 beta (build 17451)
    Exception occurred at: 00070EBB
    EAccessViolation: Access violation.
    BackTrace:
    $0007105D TMONITOR.GETWORKAREARECT, line 62 of monitor.inc
    $00203DD3 TVIEWFORM.INITDEFAULTSIZE, line 1123 of FrmView
    $002022B6 TVIEWFORM.CREATE, line 426 of FrmView
    $001AFAFA BCPROCESSCMDLINE, line 1815 of BcStartup
    $001A9D4A CARBONPROCESSCMDLINE, line 382 of BcStartup
    $00077009 TAPPLICATION.PROCESSASYNCCALLQUEUE, line 1079 of application.inc
    $00075318 TAPPLICATION.IDLE, line 389 of application.inc
    $0007D929 TBCCARBONWIDGETSET.HANDLEMESSAGE, line 79 of Interfaces
    $0017CBB9 TBCAPPLICATION.HANDLEMESSAGE, line 2129 of BcForms
    $000A92C7 THREADMANAGERSTARTPROC, line 1105 of cMicroThreads
    $9BD475FB
    $9BD47485
    $9BD4CCF2
    What to do??
    Juergen
  • Zoë
    Team Scooter
    • Oct 2007
    • 2666

    #2
    Did you add, remove, or change you monitor configuration while BC was running?
    Zoë P Scooter Software

    Comment

    • Juergen
      Visitor
      • Jan 2014
      • 6

      #3
      No, but I might have closed the MacBook while BC was running

      Comment

      • Juergen
        Visitor
        • Jan 2014
        • 6

        #4
        No, I just closed the macbook while BC was running

        Comment

        • Aaron
          Team Scooter
          • Oct 2007
          • 15997

          #5
          Was there an external monitor connected to the Macbook?
          Aaron P Scooter Software

          Comment

          • Juergen
            Visitor
            • Jan 2014
            • 6

            #6
            there was no monitor connected

            Comment

            • Aaron
              Team Scooter
              • Oct 2007
              • 15997

              #7
              At any point? From beginning to end it was a single laptop, no external monitor? That's interesting, given the stack trace. We have a potential fix in the next release, but we have not reproduced this crash in house yet.

              Are there any customization options you've made in OSX when closing your lid? What kind of macbook are you using and what resolution does its monitor run at? Which version of OSX are you running (10.X.X)?
              Aaron P Scooter Software

              Comment

              • Juergen
                Visitor
                • Jan 2014
                • 6

                #8
                I own the MacBook Pro 10.1 as a second hand MacBook for two months and have since then never attached any external monitor. It runs with 2.3 GHz i7 processor and SSD 256E. OS X 10.9.1 (13B42). I have never done any customization. Resolution mentioned in machine is "best retina" which should be for my 15,4 inch 2880 x 1800. Anything else you like to know?

                Comment

                • Aaron
                  Team Scooter
                  • Oct 2007
                  • 15997

                  #9
                  Thanks. We have a potential fix in the next minor release of the BC4 beta. If you would like to try it earlier to see if this is fixed, email us at [email protected] with a link to this forum thread, and I can send you a nightly build.
                  Aaron P Scooter Software

                  Comment

                  • Juergen
                    Visitor
                    • Jan 2014
                    • 6

                    #10
                    That'll be great! I have sent you a separate email already. Thank you!

                    Comment

                    • paulie
                      Journeyman
                      • Feb 2014
                      • 13

                      #11
                      I think I have the same problem with build 17628 (on Mavericks MacBookPro). I didn't get a crash message:I just noticed that BC was no longer running. When I started it back up, it hadn't saved my last session. I do switch monitors: I have two desks, both with different external monitors, and I also use the built in monitor sometimes.

                      Comment

                      • Aaron
                        Team Scooter
                        • Oct 2007
                        • 15997

                        #12
                        Thanks, Paulie. Could you go into more detail on how you switch between your desks? Is your computer laptop normally closed the entire time, you travel to a new desk, and then plug in devices (monitor, mouse, and keyboard)? Does this cause the laptop to wake up, or do you prevent your laptop from sleeping with the lid closed?
                        Aaron P Scooter Software

                        Comment

                        • dgarratt
                          Journeyman
                          • Sep 2013
                          • 19

                          #13
                          Seems quite similar to the problem I was having when changing the default print queue between starting and closing BC4. Does BC4 need to take a snapshot of the current hardware on startup ?

                          Comment

                          • Aaron
                            Team Scooter
                            • Oct 2007
                            • 15997

                            #14
                            It might be related, but it is hard to say without more details. We did find some areas in our Printer handling that we are looking into. Without a crash report, we'll need to look into the specifics of what might have caused the application to crash/close like that.
                            Aaron P Scooter Software

                            Comment

                            Working...