Workaround for shared memory leakage. #402
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of problem:
vncviewer creates a shared memory segment for MIT-SHM. It is not removed when vncviewer is killed
by signal, because PlatformPixelBuffer destructor is never called after CleanupSignalHandler().
Workaround:
Mark the shared memory as "destroyed" as soon as possible.
It will be invisible soon after the vncviewer is killed.
See https://bugzilla.redhat.com/show_bug.cgi?id=1358090