You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.

Bug #362: Conflict with Rogue Amoeba Airfoil

Kind bug
Product Synergy Advance
When Created , updated
Status open
Reporter Greg Hurrell
Tags no tags

Description

There seems to be a conflict between Airfoil (by Rogue Amoeba) and Synergy Advance. I got some emails from a customer that is seeing a lot of erratic crashes and hangs in Synergy Advance. All of the crash logs look different but all of the crashes are occurring deep down in the system APIs (about the only Synergy Advance code that appears in the stack trace is "main").

From the customer's email:

"The program that's causing the problem is Airfoil. It uses the same engine(?) as Audio Hijack but to a more specialized end. And yes, it does seem to be part of the problem. Even if Synergy Advanced doesn't outright crash while it's running, it does hang after a short period of time: spinning beach ball if I move the cursor over the menu bar icon, "Application Not Responding" in the dock. If I quit Airfoil (written by Rogue Amoeba) and relaunch Synergy Advanced, life is good again."

I've opened this report with the hope that we can gather information from Rogue Amoeba and figure out what the exact nature of the conflict is and how it can be worked around. Will attach some crash reports to this issue.

Comments

  1. Greg Hurrell

    Created an attachment (id=48) Crash log

  2. Greg Hurrell

    Just a note; one possible theory as to the nature of the conflict:

    Synergy Advance does a "poseAsClass" on NSThread very early on in the execution of the program (ie. in "main") so that it can provide some useful thread information (it doesn't actually change behaviour, it just provides some conveniences methods for reporting info). Observations:

    1. The stack traces of these crashes are entirely composed of system routines (ie .NSApplicationMain is being called, lots of system methods follow suit, and execution does not even get to any Synergy Advance code before the crash occurs.

    2. Airfoil/APE appear as separate threads in the thread listing.

    3. The crashes occur only when Airfoil is running.

    4. The only code run before NSApplicationMain is a poseAsClass (NSThread).

    5. It therefore seems likely that my Airfoil is doing something thread-related that is causing the crash.

    I'll need more information from the developers in order to pursue this further. Perhaps they are doing a poseAsClass as well, or something even lower-level.

  3. Greg Hurrell

    Changing assignment to reflect my new email address.

    https://wincent.dev/a/news/archives/2006/05/change_of_email.php

Add a comment

Comments are now closed for this issue.

Menu