Fix out-of-bounds indexation in BundleAdjuster::ParameterizeVariables#178
Merged
lpanaf merged 1 commit intocolmap:mainfrom May 7, 2025
Merged
Fix out-of-bounds indexation in BundleAdjuster::ParameterizeVariables#178lpanaf merged 1 commit intocolmap:mainfrom
lpanaf merged 1 commit intocolmap:mainfrom
Conversation
lpanaf
approved these changes
May 7, 2025
uptycs-rmack
pushed a commit
to uptycs-rmack/glomap
that referenced
this pull request
Jan 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I was sometimes getting this runtime error during BA:
The crash exhibited a stochastic behavior across multiple executions with the same input data. It was happening only during the BA that is run after the retriangulation stage (not the first BA).
I noticed that this error occurs because
image_t center;is default initialized (to some garbage value) and its value is set toimage_idonly if the conditionif (counter == 0)is met. However, it might be the case where its value is never set (because that condition isn't met) and we end up indexingimageswith a very high value (14227666in some experiments I did). This of course causes an out-of-bunds indexation that triggers the error from Ceres.I just propose to check if
counterisn't 0 to know if the value ofcenterwas set before the call toSetParameterBlockConstant.