Skip to content

set 0 to resolution for fix uninitialised memory usage (in rare cases) #7

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
Open
nl78 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

set 0 to resolution for fix uninitialised memory usage (in rare cases) #7

nl78 wants to merge 1 commit into from

Conversation

@nl78
Copy link
Contributor

@nl78 nl78 commented Jan 2, 2026

No description provided.

@nl78 nl78 linked an issue Jan 2, 2026 that may be closed by this pull request
uninitialized memory usage #3
Open
@nl78 nl78 requested a review from bmenne-dspace January 12, 2026 19:31
@klausschuch
Copy link
Contributor

klausschuch commented Jan 13, 2026

This initialization fixes your immediate problem.
However, I think the code should be changed a bit more to not set qualifiers based on numerical values.
I introduced this check back then to just quickly get the demo running.
I'll propose an additional change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@bmenne-dspace bmenne-dspace bmenne-dspace approved these changes

@ClemensB ClemensB Awaiting requested review from ClemensB

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

uninitialized memory usage

4 participants

@nl78 @klausschuch @bmenne-dspace