Skip to content

Potential fix for frame-job hang after stale delegate release - #24

Closed
johnpetersa19 wants to merge 1 commit into
Nycolazs:mainfrom
johnpetersa19:issue-23-frame-job-fallback
Closed

johnpetersa19 wants to merge 1 commit into
Nycolazs:mainfrom
johnpetersa19:issue-23-frame-job-fallback

Conversation

@johnpetersa19

Copy link
Copy Markdown

Summary\n\nThis proposes a narrowly scoped recovery for the hard freeze reported in #23. The hang dump indicates that a late release can encounter the owner's frame job after it has already been reset to its base vtable, while the owner completion flag remains clear and the main thread waits on the associated condition variable.\n\nWhen that exact stale-job state is detected (embedded owner/job layout, base vtable, no delegate, single reference, owner unlocked, and completion not yet set), this change atomically marks the owner complete and notifies one waiter. Other delegate cases retain their existing behavior.\n\n## Validation\n\n- make: 'build/rt/hle/delegate_null.o' está atualizado. \n- \n\nThis has not yet been verified on the affected Android device; the proposed recovery may drop the stale frame job's work, as described in the issue.

Recover the owner's completion state and notify its condition variable when a late release finds the single-reference frame job already wiped. Keep the fallback limited to the reported stale-job state.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
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.

1 participant