8000 macOS: Session tracks aren't loaded when Corelyzer is launched through CML session file · Issue #18 · corewall/corelyzer · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

macOS: Session tracks aren't loaded when Corelyzer is launched through CML session file #18

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.

Sign up for GitHub

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

Jump to bottom
Open
sorghumking opened this issue Nov 25, 2020 · 1 comment
Open

macOS: Session tracks aren't loaded when Corelyzer is launched through CML session file #18

sorghumking opened this issue Nov 25, 2020 · 1 comment

Comments

@sorghumking
Copy link
Collaborator

When a CML session file is used to invoke Corelyzer (via double-click, right-click + Open, or dragging CML file onto Corelyzer app), the session loads incompletely. Data files are added correctly, but tracks and sections don't appear.

CorelyzerAppController.doAssociatedFile() calls loadStateFile(). This eventually leads to CorelyzerAppController.createTrack(), where the SceneGraph.addTrack() call returns -1 instead of a valid, non-negative ID.

However, if I create a Runnable with Thread.sleep(2000) before calling loadStateFile(), everything works correctly.

So it appears the problem is a race condition: we try to add a track before SceneGraph is ready.

To fix, ensure app initialization is complete, then load the CML file.
@sorghumking
Copy link
Collaborator Author

Included the crude "sleep 2000ms" workaround in 2.1.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sorghumking
0