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

Constellation panic caused by assertions #11309

Closed
asajeffrey opened this issue May 20, 2016 · 2 comments
Closed

Constellation panic caused by assertions #11309

asajeffrey opened this issue May 20, 2016 · 2 comments
Assignees

Comments

@asajeffrey
Copy link
Member

@asajeffrey asajeffrey commented May 20, 2016

We allow assert! and assert_eq! in the constellation. If these assertions fail, they will cause the constellation to crash, without providing any way for the user to submit a crash report. See, e.g. #11298.

If we decide not to allow such assertions, we should add a check to etc/ci/check_no_unwrap.sh (@aneeshusa).

@asajeffrey
Copy link
Member Author

@asajeffrey asajeffrey commented May 20, 2016

The easiest thing to do would be to replace assert by debug_assert, anyone running a debug build can probably work out how to submit a crash report from a raw panic. This would just hide a failed assert though, should we try to throw a mozbrowsererror event instead? (@paulrouget)

@nox
Copy link
Member

@nox nox commented Oct 1, 2017

We made constellation panic way less, and the general motto for constellation is to panic there. I think this can be closed now.

@nox nox closed this Oct 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.