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.

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

Segfaults with ACE + J1.7 #81

Open
cortner opened this issue Dec 7, 2021 · 5 comments
Open

Segfaults with ACE + J1.7 #81

cortner opened this issue Dec 7, 2021 · 5 comments

Comments

@cortner
Copy link
Member

cortner commented Dec 7, 2021 •
edited
Loading

test_admodel.jl has a segfault when Zygoting the loss w.r.t. the model. (indicated in comments on main branch)
cortner added a commit that referenced this issue Dec 7, 2021
@cortner
commented out segaulting test; cf #81
3eda4ca
@cortner
Copy link
Member Author

cortner commented Dec 28, 2021 •
edited
Loading

This is still a problem in J1.7.1, and occurs only when running as part of the test suite, not when run "manually" within VS Code, or by simply executing the test file as a script.

@cortner
Copy link
Member Author

cortner commented Dec 31, 2021

Some updates - it seems this occurs only with O3 and forcing bounds checking. How weird is that? Also, one moment it is reproducible, next it is not... I don't like it.

@cortner
Copy link
Member Author

cortner commented Jan 3, 2022

... and now I can't reproduce it anymore...

@cortner
Copy link
Member Author

cortner commented Jan 13, 2022

This still appears to happen, now opened a discussion at Discourse but nobody seems interested.

@cortner cortner changed the title Segfault with ACE + Zygote + J1.7 Segfaults with ACE + J1.7 Feb 2, 2022
@cortner
Copy link
Member Author

cortner commented Feb 2, 2022 •
edited
Loading

no longer clear that Zygote is the culprit. segfaults happen randomly all over the place. It seems that using Rosetta-Julia 1.7 resolves the issue for now? But maybe this is random too?

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
@cortner