Page 1 of 4 123 ... LastLast
Results 1 to 10 of 33
  1. #1
    Join Date
    Jun 2018
    Posts
    3

    Default macOS 10.14 Mojave - Beta Issues

    It appears that Beyond Compare 4.2.5 (build 23088) isn't fully compatible with macOS 10.14 beta (18A293u), causing app crashes. Will the BC dev team be investigating / releasing beta updates anytime soon?

  2. #2
    Join Date
    Oct 2007
    Location
    Madison, WI
    Posts
    4,728

    Default

    We've had one other customer report crashes on macOS 10.14 Mojave beta and we are investigating.

    macOS 10.13 beta also caused BC to crash due to debug code in the beta. The crash was fixed on Apple's end when 10.13 was officially released without the debugging code enabled.

    For the crashes you're seeing, is BC crashing on startup, or is it crashing during specific actions?

    If an error message or crash information is displayed, please post it here or email it to support@scootersoftware.com.
    Chris K Scooter Software

  3. #3
    Join Date
    Oct 2007
    Location
    Madison, WI
    Posts
    4,728

    Default

    I discussed it with our Mac developer. Because the crashes are specific to a beta OS version, it's unlikely we'll release a bug fix. If there are still crash issues when 10.14 is officially released, then we'll release a fixed version of BC. If it's like 10.13 beta, then the official release of 10.14 might fix the crash without requiring code changes on our end.
    Chris K Scooter Software

  4. #4
    Join Date
    Jun 2018
    Posts
    3

    Default

    Quote Originally Posted by Chris View Post
    For the crashes you're seeing, is BC crashing on startup, or is it crashing during specific actions?
    Still occurring with macOS 10.14 beta 2 (18A314h)
    Crash occurs during usage. ex. folder compare then view differences between files.

    Details:
    Code:
    Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes:       KERN_PROTECTION_FAILURE at 0x00000000bf7ffff8
    Exception Note:        EXC_CORPSE_NOTIFY
    
    Termination Signal:    Segmentation fault: 11
    Termination Reason:    Namespace SIGNAL, Code 0xb
    
    Application Specific Information:
    *** CFRelease() called with NULL ***
    
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   com.ScooterSoftware.BeyondCompare	0x0003854c 0x10000 + 165196
    1   com.ScooterSoftware.BeyondCompare	0x000aa7d4 0x10000 + 632788
    2   com.ScooterSoftware.BeyondCompare	0x000251af 0x10000 + 86447
    3   com.ScooterSoftware.BeyondCompare	0x000347fc 0x10000 + 149500
    4   com.ScooterSoftware.BeyondCompare	0x000250e7 0x10000 + 86247
    5   com.ScooterSoftware.BeyondCompare	0x000250e7 0x10000 + 86247
    6   com.ScooterSoftware.BeyondCompare	0x000250e7 0x10000 + 86247
    7   com.ScooterSoftware.BeyondCompare	0x000250e7 0x10000 + 86247
    8   com.ScooterSoftware.BeyondCompare	0x000250e7 0x10000 + 86247
    9   com.ScooterSoftware.BeyondCompare	0x000250e7 0x10000 + 86247
    10  com.ScooterSoftware.BeyondCompare	0x000250e7 0x10000 + 86247
    11  com.ScooterSoftware.BeyondCompare	0x000250e7 0x10000 + 86247
    12  com.ScooterSoftware.BeyondCompare	0x000250e7 0x10000 + 86247
    13  com.ScooterSoftware.BeyondCompare	0x000250e7 0x10000 + 86247
    14  com.ScooterSoftware.BeyondCompare	0x00034f75 0x10000 + 151413
    15  com.ScooterSoftware.BeyondCompare	0x00011825 0x10000 + 6181

  5. #5
    Join Date
    Oct 2007
    Location
    Madison, WI
    Posts
    4,728

    Default

    Thank you for sharing the crash information. It's unlikely we'll release a fix for macOS 10.14 beta. If the issue persists in the official release of 10.14, we'll issue a fix at that time.
    Chris K Scooter Software

  6. #6
    Join Date
    Jun 2018
    Posts
    4

    Default

    Quote Originally Posted by Chris View Post
    Thank you for sharing the crash information. It's unlikely we'll release a fix for macOS 10.14 beta. If the issue persists in the official release of 10.14, we'll issue a fix at that time.
    Disagree!! At least you guys should do some investigation and figure out why it's crashing.

    I'm going to request a refund, if you're not issue a fix on this, because it stop functioning anymore, and I can't work around it.

  7. #7
    Join Date
    Oct 2007
    Location
    Madison, WI
    Posts
    11,890

    Default

    As Chris mentions above, we know why it is crashing: MacOS beta debug code which conflicts with BC4, which also happened last time there was a MacOS beta.

    Unfortunately, during the beta period, this code frequently changes, which causes it to break again each time. The frequent updates required to workaround the debug code changes, where last time we kept up with the beta changes it required full time work, preventing other bug fixes and enhancement work. On top of that, there is also a decent amount of downtime for users, since re-implementing the workaround of debug code takes time, and still requires QA and Release workflow, sometimes not quick enough to keep up with the next code shift. This also lead to user frustration, since we had releases that "supported MacOS beta" that then also wouldn't work later, which also varied depending on if the user was updating the MacOS beta build and BC4 concurrently.

    And once the full release was available and all of the MacOS beta debug code is removed, BC4 resumed working.

    To reiterate: we know why it is crashing, but the fix is not quickly deployable to keep up with the shifts present in the MacOS beta release. We're tracking it, anticipate it will resolve itself, while also having a patch ready for the Release Candidate once that is made available. If you need to use BC4 during this time period, please use the most recent release of MacOS instead of the beta.
    Aaron P Scooter Software

  8. #8
    Join Date
    Jun 2018
    Posts
    4

    Default

    Quote Originally Posted by Aaron View Post
    As Chris mentions above, we know why it is crashing: MacOS beta debug code which conflicts with BC4, which also happened last time there was a MacOS beta.

    Unfortunately, during the beta period, this code frequently changes, which causes it to break again each time. The frequent updates required to workaround the debug code changes, where last time we kept up with the beta changes it required full time work, preventing other bug fixes and enhancement work. On top of that, there is also a decent amount of downtime for users, since re-implementing the workaround of debug code takes time, and still requires QA and Release workflow, sometimes not quick enough to keep up with the next code shift. This also lead to user frustration, since we had releases that "supported MacOS beta" that then also wouldn't work later, which also varied depending on if the user was updating the MacOS beta build and BC4 concurrently.

    And once the full release was available and all of the MacOS beta debug code is removed, BC4 resumed working.

    To reiterate: we know why it is crashing, but the fix is not quickly deployable to keep up with the shifts present in the MacOS beta release. We're tracking it, anticipate it will resolve itself, while also having a patch ready for the Release Candidate once that is made available. If you need to use BC4 during this time period, please use the most recent release of MacOS instead of the beta.
    It's too funny, you don't have to make an official release on a beta OS. Why not release a beta though?

    "during the beta period, this code frequently changes, which causes it to break again each time."
    ^^ and if that happens each individual beta update, it sounds like technically you're doing something wrong. Don't try to find an excuse for the laziness.

    Most of your customers are software developers, and most of us are working with Beta products all the time, because we need to keep the development moving closely with high compatibilities with all other products. A product should be kept development and updating all the time, that is how a modern software development should be, unless you want to retire your product.
    Last edited by ericvan76; 03-Jul-2018 at 12:04 AM.

  9. #9
    Join Date
    Jul 2018
    Posts
    1

    Default

    Quote Originally Posted by ericvan76 View Post
    It's too funny, you don't have to make an official release on a beta OS. Why not release a beta though?

    "during the beta period, this code frequently changes, which causes it to break again each time."
    ^^ and if that happens each individual beta update, it sounds like technically you're doing something wrong. Don't try to find an excuse for your laziness.

    Most of your customers are software developers, and most of us are working with Beta products all the time, because we need to keep the development moving closely with high compatibilities with all other products. A product should be kept development and updating all the time, that is how a modern software development should be, unless you want to retire your product.
    Agree.

  10. #10
    Join Date
    Oct 2007
    Location
    Madison, WI
    Posts
    11,890

    Default

    We're working on a permanent solution to avoid this scenario, but we'll work on if there's anything else we can do to work around the current beta issue.
    Aaron P Scooter Software

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •