Repository navigation
Release terrain and shadow shader objects after linking - #96
Merged
Merged
Conversation
relh
marked this pull request as draft
October 5, 2026 02:00
…proof Co-authored-by: Codex GPT-6 <noreply@openai.com>
relh
marked this pull request as ready for review
October 5, 2026 20:54
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Detach and delete compiled vertex and fragment shaders after linking the terrain and shadow programs. The linked programs retain their executable code and link diagnostics.
Validation: both builders passed a temporary Mesa software-OpenGL check: three successful links each, zero attached shaders, exact red-pixel rendering, program deletion, and no GL errors. The proposed diff contains only the two shader-lifetime fixes.