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

Segfault if Omicam exits while connected to Omicontrol #4

Open
mattyoung101 opened this issue Oct 30, 2019 · 1 comment
Open

Segfault if Omicam exits while connected to Omicontrol #4

mattyoung101 opened this issue Oct 30, 2019 · 1 comment
Assignees
Labels
Low Priority Only attempt if time permits and willing.

Comments

@mattyoung101
Copy link
Owner

Occasionally Omicam will segfault on exit, and ASan says it's a heap use after free, however, it got stuck printing the backtrace so I don't know where it's coming from.

Low priority because it's difficult to replicate and doesn't matter too much as it's only segfaulting on exit, after cleaning everything else up (it happens after the log file is closed too).

@mattyoung101 mattyoung101 added the Low Priority Only attempt if time permits and willing. label Oct 30, 2019
@mattyoung101 mattyoung101 self-assigned this Oct 30, 2019
@mattyoung101
Copy link
Owner Author

If I recall correctly this is related to the remote debugger module, and occurs only when it's connected to Omicontrol and Omicam exits which is a rare situation (shouldn't ever happen in production).

@mattyoung101 mattyoung101 added the Can't Repro Difficult or no longer possible to reproduce. label Dec 18, 2019
@mattyoung101 mattyoung101 removed the Can't Repro Difficult or no longer possible to reproduce. label Jan 2, 2020
@mattyoung101 mattyoung101 changed the title Rare heap-use-after-free on exit Segfault if Omicam exits while connected to Omicontrol Jan 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Low Priority Only attempt if time permits and willing.
Projects
None yet
Development

No branches or pull requests

1 participant