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

Framebuffer Release #30

Open
ztnel opened this issue Dec 1, 2021 · 1 comment
Open

Framebuffer Release #30

ztnel opened this issue Dec 1, 2021 · 1 comment
Assignees
@BrandonLucasZhu @ztnel
Labels
invalid This doesn't seem right system os/system interfaces

Comments

@ztnel
Copy link
Member

ztnel commented Dec 1, 2021

Description

For any process interruption signal, pygame must be gracefully exited to release the framebuffer. If this does not happen pygame does not release the device even when the process is terminated. This makes running secondary instances of the app hang due to the frame buffer being occupied by the previous instance. For some solutions see the link here: https://www.py4u.net/discuss/209214
@ztnel ztnel added invalid This doesn't seem right system os/system interfaces labels Dec 1, 2021
@ztnel
Copy link
Member Author

ztnel commented Dec 6, 2021

@BrandonLucasZhu assigning you, gauge by interest.

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

@BrandonLucasZhu BrandonLucasZhu

@ztnel ztnel

Labels
invalid This doesn't seem right system os/system interfaces
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@BrandonLucasZhu @ztnel