Skip to content

gltrim: retain objects in the last frame that were created in earlier frames #807

Merged
jrfonseca merged 1 commit into
apitrace:masterfrom
gerddie:gltrim-make-last-frame-replayable
Jun 28, 2022
Merged

gltrim: retain objects in the last frame that were created in earlier frames #807
jrfonseca merged 1 commit into
apitrace:masterfrom
gerddie:gltrim-make-last-frame-replayable

Conversation

@gerddie

@gerddie gerddie commented Jun 23, 2022

Copy link
Copy Markdown
Contributor

In order to be able to loop the last frame we must not destroy objects
that are used in the last frame but not created there. For simplicity
only check whether the object was created in the last frame, and not
emit the delete code if it was not.

Remark:
This doesn't cover all cases where looping the last frame will fail, e.g. buffer mappings or context creation and destruction may also lead to crashes.

…arlier frames

In order to be able to loop the last frame we must not destroy objects
that are used in the last frame but not created there. For simplicity
only check whether the object was created in the last frame, and not
emit the delete code if it was not.

Signed-off-by: Gert Wollny <gert.wollny@collabora.com>
@gerddie gerddie force-pushed the gltrim-make-last-frame-replayable branch from babff26 to cb39c17 Compare June 23, 2022 09:27
@jrfonseca

Copy link
Copy Markdown
Member

Looks reasonable to me.

@jrfonseca jrfonseca merged commit eccf3c8 into apitrace:master Jun 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants