Skip to content

Conversation

@fedejeanne
Copy link
Member

For the unlikely (but possible) case in which the callback is executed too late and the browser/display has already been disposed.

@github-actions
Copy link
Contributor

github-actions bot commented Aug 11, 2025

Test Results

   546 files  ±0     546 suites  ±0   37m 31s ⏱️ + 8m 21s
 4 425 tests ±0   4 408 ✅ ±0   17 💤 ±0  0 ❌ ±0 
16 746 runs  ±0  16 619 ✅ ±0  127 💤 ±0  0 ❌ ±0 

Results for commit a513d45. ± Comparison against base commit 10cc2e6.

♻️ This comment has been updated with latest results.

@fedejeanne fedejeanne force-pushed the check_browser_disposed_in_callback branch from d02d6d1 to 7bfc170 Compare August 11, 2025 14:25
For the unlikely (but possible) case in which the callback is executed
too late and the browser/display has already been disposed.

Add a new private method to funnel all calls to Display::asyncExec and
check there if the display is still usable.
@HeikoKlare HeikoKlare force-pushed the check_browser_disposed_in_callback branch from 7bfc170 to a513d45 Compare August 11, 2025 14:43
@HeikoKlare HeikoKlare merged commit 97c24b9 into eclipse-platform:master Aug 11, 2025
17 checks passed
@HeikoKlare HeikoKlare deleted the check_browser_disposed_in_callback branch August 11, 2025 15:02
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.

Edge: Widget disposed exceptions

2 participants