Skip to content

Conversation

@ltratt
Copy link
Member

@ltratt ltratt commented Jan 3, 2025

For some reason, it didn't occur to me that collecting repairs can take a very, very long time: it's possible for this to take so long that it exceeds any reasonable memory limit. Foolishly, I had realised that rank_rprs needed a timeout, but I hadn't applied that to collect_repairs. This commit does that, ensuring that the user's input is less likely to cause grmtools to consume too much memory.

Fixes #481.

For some reason, it didn't occur to me that collecting repairs can take
a very, very long time: it's possible for this to take so long that it
exceeds any reasonable memory limit. Foolishly, I *had* realised that
`rank_rprs` needed a timeout, but I hadn't applied that to
`collect_repairs`. This commit does that, ensuring that the user's input
is less likely to cause grmtools to consume too much memory.
@ratmice ratmice added this pull request to the merge queue Jan 3, 2025
Merged via the queue into softdevteam:master with commit 6967d50 Jan 3, 2025
2 checks passed
@ltratt ltratt deleted the timeout_collect branch February 3, 2025 18:33
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.

grmtools exceeds timeout and crashes

2 participants