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

Investigate SEGV on unknown address #12

Closed
seanlinsley opened this issue Jul 19, 2022 · 2 comments · Fixed by #22
Closed

Investigate SEGV on unknown address #12

seanlinsley opened this issue Jul 19, 2022 · 2 comments · Fixed by #22

Comments

@seanlinsley
Copy link
Member

The parallel test as currently written opens 10,000 threads that each call out to libpg_query at the same time. This error happens rarely, and so far only on CI.

https://github.com/pganalyze/pg_query.rs/runs/7419661487

LeakSanitizer:DEADLYSIGNAL
==4846==ERROR: LeakSanitizer: SEGV on unknown address 0x7f7999ae3ff8 (pc 0x5607592a63f4 bp 0x7f7595e56e60 sp 0x7f7595e565f0 T16383)
==4846==The signal is caused by a READ memory access.

Screen Shot 2022-07-19 at 6 43 13 PM
@seanlinsley
Copy link
Member Author

Another failed build: https://github.com/pganalyze/pg_query.rs/runs/7530042546?check_suite_focus=true#step:6:321

@seanlinsley
Copy link
Member Author

And another: https://github.com/pganalyze/pg_query.rs/actions/runs/3894507509/jobs/6648591678

@seanlinsley seanlinsley linked a pull request Jul 25, 2023 that will close this issue
Fix LeakSanitizer segfault #22
Merged
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

Successfully merging a pull request may close this issue.

Fix LeakSanitizer segfault pganalyze/pg_query.rs
1 participant
@seanlinsley