Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[NUI] Make DaliAccessibilityDetachAccessibleObject called at main thread #5674

Merged
merged 1 commit into from
Oct 30, 2023

Conversation

hinohie
Copy link
Contributor

@hinohie hinohie commented Oct 30, 2023

void Dispose(bool) can be called from worker thread, when disposing value is false.

To ensure we detach AccessibileObject in main thread, let we remove it at Dispose(DisposeTypes), instead of Dispose(bool)

Copy link
Contributor

@dongsug-song dongsug-song left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good to me

void Dispose(bool) can be called from worker thread, when disposing value is false.

To ensure we detach AccessibileObject in main thread, let we remove it
at Dispose(DisposeTypes), instead of Dispose(bool).

To avoid this kind of error in future, let we remove View.Dispose(bool)
and let we only use Dispose(DisposeTypes).

Signed-off-by: Eunki, Hong <[email protected]>
@Seoyeon2Kim
Copy link
Contributor

@lol-github @aswigon @m-bialota
Could you check this PR even if this PR is merged soon?
If the View is disposed by GC, Interop.ControlDevel.DaliAccessibilityDetachAccessibleObject function could be called from GC thread, which could cause a crash.
This PR makes it to operate only on the main thread.

@TizenAPI-Bot
Copy link
Collaborator

Internal API Changed

Added: 0, Removed: 1, Changed: 0

Removed

- /// <since_tizen>none</since_tizen
- [EditorBrowsable(EditorBrowsableState.Never)]
- System.Void Tizen.NUI.BaseComponents.View::Dispose(System.Boolean)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants