You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd submit this as a PR, but my fork is a mess, so this might be quickest. It only seems to need a very small fix.
The problem is first mentioned here and again further down. I'm fairly certain I've seen this issue in my own plugins, where they use external textures.
It's basically an ownership issue. During a close or relaunch, the arrays here wrongly tidy up resources they hold, even though those should only be transient, so with some unlucky timing you'll get double-frees. Basically, you have to be creating or updating a resource on the final frame; I suppose this must mean the issue can happen more generally--complete with mysterious bug reports in the past 😃--but the frequent updates in these sorts of plugins ramp up the probability.
The problem seems to be resolved by replacing the linked line and the next one thus:
Hi.
I'd submit this as a PR, but my fork is a mess, so this might be quickest. It only seems to need a very small fix.
The problem is first mentioned here and again further down. I'm fairly certain I've seen this issue in my own plugins, where they use external textures.
It's basically an ownership issue. During a close or relaunch, the arrays here wrongly tidy up resources they hold, even though those should only be transient, so with some unlucky timing you'll get double-frees. Basically, you have to be creating or updating a resource on the final frame; I suppose this must mean the issue can happen more generally--complete with mysterious bug reports in the past 😃--but the frequent updates in these sorts of plugins ramp up the probability.
The problem seems to be resolved by replacing the linked line and the next one thus:
Without analyzing it too deeply, I think the
GPUResource*
array (fDestroyQueue
) is fine, since its contents were after all queued to be destroyed.The text was updated successfully, but these errors were encountered: