Skip to content

internal/mux: p.bufPool might be null when calling the freeing closure at getTmpBuf #258

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
Closed
hajimehoshi opened this issue Mar 23, 2025 · 0 comments
Closed

internal/mux: p.bufPool might be null when calling the freeing closure at getTmpBuf #258

hajimehoshi opened this issue Mar 23, 2025 · 0 comments
Labels
bug
Milestone
v3.3.3

Comments

@hajimehoshi
Copy link
Member

See hajimehoshi/ebiten#3214
@hajimehoshi hajimehoshi added this to the v3.3.3 milestone Mar 23, 2025
hajimehoshi added a commit that referenced this issue Mar 23, 2025
@hajimehoshi
internal/mux: bug fix: crash when changing the buffer size
b371626 
Closes #258
hajimehoshi added a commit that referenced this issue Mar 23, 2025
@hajimehoshi
internal/mux: add tests
002c819 
Updates #258
hajimehoshi added a commit that referenced this issue Mar 23, 2025
@hajimehoshi
internal/mux: add tests
ca25364 
Updates #258
hajimehoshi added a commit that referenced this issue Mar 23, 2025
@hajimehoshi
internal/mux: do not put back an old buffer
07d3c9f 
Theoretically, it is possible to put an old-sized buffer to the pool.

Closes #258
hajimehoshi added a commit that referenced this issue Mar 23, 2025
@hajimehoshi
internal/mux: do not put back an old buffer
12990bb 
Theoretically, it is possible to put an old-sized buffer to the pool.

Closes #258
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
v3.3.3
Development

No branches or pull requests
1 participant
@hajimehoshi