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

"Segmentation fault" error #184

Closed
mariiak2021 opened this issue Jan 17, 2024 · 7 comments
Closed

"Segmentation fault" error #184

mariiak2021 opened this issue Jan 17, 2024 · 7 comments

Comments

@mariiak2021
Copy link

Hi @lukasalexanderweber

Thank you for the great work!
I'm having some troubles with the algorithm since yesterday and though you might provide some information.
While using stitching pipeline I'm getting error: "Segmentation fault" without any further explanation. It is not "Stitching error" and happening sometime during cropping by my tests, although I can't get precise place or understand what could cause the error. I haven't done any changes to my code since yesterday.
Will appreciate any ideas!

Best,
Mariia

@mariiak2021
Copy link
Author

I read some other errors with cropping. Should add that I'm running code on remote Linux server

@lukasalexanderweber
Copy link
Member

What do you mean with " I read some other errors with cropping. "

@mariiak2021
Copy link
Author

@lukasalexanderweber I mean other issues like #119

@lukasalexanderweber
Copy link
Member

Quite sure this isn't related to the stitching package: https://stackoverflow.com/questions/2346806/what-is-a-segmentation-fault

@mariiak2021
Copy link
Author

Hi @lukasalexanderweber you are right - I've solved segmentation error but still getting errors: free(): invalid size or munmap_chunk(): invalid pointer. Have no idea how to solve them. Can't make even one stitching.

@lukasalexanderweber
Copy link
Member

This is also really C++ specific: https://stackoverflow.com/questions/32118545/munmap-chunk-invalid-pointer.

Don't you have a way to test it locally and make sure your installation on the remote server is correct

@mariiak2021
Copy link
Author

Closing as the problem was solved!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants