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

SQLite error: database disk image is malformed #3317

Open
maher1337 opened this issue Jul 18, 2024 · 0 comments
Open

SQLite error: database disk image is malformed #3317

maher1337 opened this issue Jul 18, 2024 · 0 comments

Comments

@maher1337
Copy link

Describe the bug
When is sequential feature matching.

I0718 20:00:47.199163 64287 pairing.cc:318] Matching image [2261/29302]
E0718 20:00:47.207983 64287 database.cc:749] SQLite error: database disk image is malformed
terminate called after throwing an instance of 'std::runtime_error'
what(): SQLite error: database disk image is malformed
*** Aborted at 1721332847 (unix time) try "date -d @1721332847" if you are using GNU date ***
PC: @ 0x0 (unknown)
*** SIGABRT (@0x3e80000fb17) received by PID 64279 (TID 0x7da495583000) from PID 64279; stack trace: ***
@ 0x7da4ba3a9046 (unknown)
@ 0x7da4b8242520 (unknown)
@ 0x7da4b82969fc pthread_kill
@ 0x7da4b8242476 raise
@ 0x7da4b82287f3 abort
@ 0x7da4b86a2b9e (unknown)
@ 0x7da4b86ae20c (unknown)
@ 0x7da4b86ae277 std::terminate()
@ 0x7da4b86ae4d8 __cxa_throw
@ 0x5f03c5f7027e colmap::SQLite3CallHelper()
@ 0x5f03c5f6667d colmap::Database::WriteMatches()
@ 0x5f03c5f66987 colmap::Database::WriteMatches()
@ 0x5f03c640bda8 colmap::FeatureMatcherCache::WriteMatches()
@ 0x5f03c5f2d127 colmap::FeatureMatcherController::Match()
@ 0x5f03c5f1ee39 colmap::(anonymous namespace)::GenericFeatureMatcher<>::Run()
@ 0x5f03c5fcd9b0 colmap::Thread::RunFunc()
@ 0x7da4b86dc253 (unknown)
@ 0x7da4b8294ac3 (unknown)
@ 0x7da4b8326850 (unknown)
Aborted (core dumped)

To Reproduce
Steps to reproduce the behavior:
Use ns-process-data images --camera-type equirectangular --images-per-equirect 14 --crop-factor 0 0.2 0 0 --data optimized_max --output-dir nerf_extracted_frames
The folder contains about 2092 frames in a 1280x640 resolution taken from a video

Expected behavior
It should work as expected, matching features and not causing any database corruption to cocur.

Screenshots
N/A

Additional context
I'm guessing the multi-writes from CUDA could be the reason. I'm looking into how I can solve that to bypass this issue

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

1 participant