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

initialize errors HashSet without high initial capacity #532

Merged
merged 1 commit into from
Apr 7, 2024

Conversation

fabianbees
Copy link
Contributor

@fabianbees fabianbees commented Jan 6, 2024

In most cases it is not expected to have that many errors, which causes an increase of the HashSet, it shouldn't be necessary to pre-allocate that much memory for potential errors.

fixes #447
fixes #523

Copy link
Owner

@bee-san bee-san left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

commenting to see if CI will run... it is not?

@bee-san
Copy link
Owner

bee-san commented Apr 6, 2024

Hi! Mind pushing an empty commit? CI has failed to pick this up and I think it'll only pick it up on a new commit? 🤔

@fabianbees fabianbees force-pushed the reduce_mem_footprint branch from 133a4b3 to 138ceed Compare April 7, 2024 06:54
@fabianbees
Copy link
Contributor Author

CI is not running, because the Build-Workflow somehow requires an approval from a maintainer:
image

@fabianbees fabianbees force-pushed the reduce_mem_footprint branch from 5a84370 to 138ceed Compare April 7, 2024 07:00
@bee-san
Copy link
Owner

bee-san commented Apr 7, 2024

CI is not running, because the Build-Workflow somehow requires an approval from a maintainer: image

Yes, that's fine. Before it wasn't running at all, and the emtpy commit kicked GitHub into seeing it had something to do here :)

CI is running!

@bee-san bee-san merged commit 1a5ff5b into bee-san:master Apr 7, 2024
11 checks passed
@bee-san
Copy link
Owner

bee-san commented Apr 7, 2024

thank you!!

@fabianbees
Copy link
Contributor Author

Your welcome! :)

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

Successfully merging this pull request may close these issues.

Rustscan crash with failed memory allocation Hash Table Overflow
2 participants