Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Opening traces via Finder launches multiple AGI instances and it can get stuck #458

Closed
pmuetschard opened this issue Sep 14, 2020 · 4 comments · Fixed by #926
Closed

Opening traces via Finder launches multiple AGI instances and it can get stuck #458

pmuetschard opened this issue Sep 14, 2020 · 4 comments · Fixed by #926
Assignees

Comments

@pmuetschard
Copy link
Member

pmuetschard commented Sep 14, 2020

On MacOS, when opening files from within Finder, while an AGI instance is already running, each time a trace file is double-clicked/opened, instead of opening that file within the already running instance, a new AGI instance is launched. This often/always results in a stuck situation, where the AGI icon keeps bouncing in the Dock, but no progress is made. When getting into this stuck mode, attempting to double-click any other file, no longer launches a new AGI instance, which makes it impossible to open any more files. When it gets stuck, you can no longer launch AGI, even by double-clicking the App.

@pmuetschard
Copy link
Member Author

Work-arounds to get out of the stuck mode:

  1. Launch AGI via the command line /Applications/AGI.app/Contents/MacOS/agi. However, the Dock remains broken.
  2. sudo killall launchservicesd; sudo killall Dock This is a bit brutal, but appears to work. I have noticed that the Dock misbehaves a bit afterwards (e.g. it stays visible on top of fullscreen content).

@pmuetschard
Copy link
Member Author

It appears, at least sometimes, that right-clicking on the bouncing icon and selecting "Force Quit" also recovers the system. It can take ~5 seconds after selecting "Force Quit" for the bouncing icon to go away and the system to recover.

@pau-baiget pau-baiget added P2 and removed P0 labels Oct 5, 2020
@pau-baiget
Copy link
Contributor

Lowering priority since we have a workaround stated in comment 2.

@zhangyiwei
Copy link
Contributor

@zhangyiwei cc myself here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants