Webview is disposed #2820
Comments
|
@afaddoul does this happen consistently? |
|
no, actually it was the first time |
|
WebView? Is it one of 2 pieces of code (WebView, Chrome) that were urgently updated by Google and caused a total Internet blackout for 7 hours until people upgraded them in my country? |
|
@PavelSosin-320 this would be the webview for our start page. I don't think this issue is at all related to the Chrome update. |
|
We're planning to revise the start page to use the new model being demonstrated in Insiders right now. |
Closed
This was referenced Apr 29, 2021
Closed
|
Pulling from Future to 1.13 since several people have reported it recently, see related issues, @dbreshears FYI |
karolz-ms
added a commit
that referenced
this issue
May 21, 2021
* Fix "webview is disposed" error Fixes issue #2820 The poblem is likely due to a handful of async calls done beteween when the start page view is created and when its content is set. That gives the user an opportunity to close the start page before we attempt to set its content. It is especially tempting since during the time the content is computed the already-visible start page panel is empty. This change front-loads that async processing so that the webview creation becomes fully synchronous.
Closed
ravipal
added a commit
that referenced
this issue
May 24, 2021
* Add malware scan (#2942) * Add malware scan. * Actually add malware scan. * Move malware task and stop immediately. * Update UI dependency for new icon. (#2955) * Update vsce dependency (#2957) * Fix "webview is disposed" error (#2959) * Fix "webview is disposed" error Fixes issue #2820 The poblem is likely due to a handful of async calls done beteween when the start page view is created and when its content is set. That gives the user an opportunity to close the start page before we attempt to set its content. It is especially tempting since during the time the content is computed the already-visible start page panel is empty. This change front-loads that async processing so that the webview creation becomes fully synchronous. * Add missing description for debug config property. (#2963) Co-authored-by: Phillip Hoff <phillip@orst.edu> Co-authored-by: Karol Zadora-Przylecki <karolz@microsoft.com>
ravipal
added a commit
that referenced
this issue
May 25, 2021
* Prepare for release (#2929) * Upgrade the vsce to 1.88 to get latest underscore (#2930) * Add extendedLocation property in Plan and Site creation (#2931) * Add extendedLocation property in Plan and Site creation * Updating comment * Ravipal/merge from main (#2964) * Add malware scan (#2942) * Add malware scan. * Actually add malware scan. * Move malware task and stop immediately. * Update UI dependency for new icon. (#2955) * Update vsce dependency (#2957) * Fix "webview is disposed" error (#2959) * Fix "webview is disposed" error Fixes issue #2820 The poblem is likely due to a handful of async calls done beteween when the start page view is created and when its content is set. That gives the user an opportunity to close the start page before we attempt to set its content. It is especially tempting since during the time the content is computed the already-visible start page panel is empty. This change front-loads that async processing so that the webview creation becomes fully synchronous. * Add missing description for debug config property. (#2963) Co-authored-by: Phillip Hoff <phillip@orst.edu> Co-authored-by: Karol Zadora-Przylecki <karolz@microsoft.com> * Update change log to includ LIMA support (#2965) * Update date on release notes (#2966) Co-authored-by: Phillip Hoff <phillip@orst.edu> Co-authored-by: Karol Zadora-Przylecki <karolz@microsoft.com>
|
This was actually fixed in 0.13 release |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Does this occur consistently?
Repro steps:
Action: vscode-docker.help.openStartPage
Error type: Error
Error Message: Webview is disposed
Version: 1.11.0
OS: darwin
OS Release: 20.3.0
Product: Visual Studio Code
Product Version: 1.54.3
Language: en
Call Stack
The text was updated successfully, but these errors were encountered: