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.

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

Investigate deadlock #11988

Closed
bep opened this issue Feb 4, 2024 · 4 comments
Closed

Investigate deadlock #11988

bep opened this issue Feb 4, 2024 · 4 comments
Assignees
@bep
Labels
Bug Outdated
Milestone
v0.123.0

Comments

@bep
Copy link
Member

bep commented Feb 4, 2024

No description provided.

@bep bep self-assigned this Feb 4, 2024
@bep bep added v0.123-DEV and removed NeedsTriage labels Feb 4, 2024
bep added a commit to bep/hugo that referenced this issue Feb 4, 2024
@bep
Handle resource changes when the resources is already evicted from cache
909b628 
Also fix a logical flaw in the cache resizer that made it too aggressive. After this I haven't been able to reproduce gohugoio#11988, but I need to look closer.

Closes gohugoio#11973
Updates gohugoio#11988
@bep bep mentioned this issue Feb 4, 2024
Merged
bep added a commit to bep/hugo that referenced this issue Feb 4, 2024
@bep
Handle resource changes when the resources is already evicted from cache
8813278 
Also fix a logical flaw in the cache resizer that made it too aggressive. After this I haven't been able to reproduce gohugoio#11988, but I need to look closer.

Closes gohugoio#11973
Updates gohugoio#11988
bep added a commit that referenced this issue Feb 4, 2024
@bep
Handle resource changes when the resources is already evicted from cache
609d798 
Also fix a logical flaw in the cache resizer that made it too aggressive. After this I haven't been able to reproduce #11988, but I need to look closer.

Closes #11973
Updates #11988
@bep
Copy link
Member Author

bep commented Feb 4, 2024

After the fix in 609d798 I haven't been able to reproduce this. I will do some more checks, but I'm not sure it really was a dead lock, I suspect it was just a situation of long wait times for obtaining a lock.

@bep bep added this to the v0.123.0 milestone Feb 5, 2024
@bep
Copy link
Member Author

bep commented Feb 5, 2024

Closing this for now.

@bep bep closed this as completed Feb 5, 2024
@bep
Copy link
Member Author

bep commented Feb 5, 2024

Note to future self: I think it's the --printMemoryUsage that makes the server lock up after a while.

@github-actions GitHub Actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@bep bep

Labels
Bug Outdated
Projects
None yet
Milestone
v0.123.0
Development

No branches or pull requests
1 participant
@bep