I am unable to properly phrase the issue, so please feel free to ask for details if I am missing anything. I have Front Matter set to open the dashboard automatically on startup of VSCode. Sometimes I close the dashboard tab before it is fully loaded. In that case, a bunch of errors pop up a little bit after that (see screenshots). I think whatever activity is running, should be "abandoned" when the tab is closed or issues with the "webview being disposed" should be caught. I do not have any additional or verbose debugging enabled, so I should not see the issues. It feels like there is some async stuff going on to populate the dashboard, that might be easily abandoned on tab-closure.
To Reproduce
Steps to reproduce the behavior:
Set dashboard to "open on startup"
start VSCode and close the dashboard tab right after it pops up
wait for it...
Expected behavior
No errors, catching the problem behind the scenes.
Screenshots
VSCode:
Version: 1.66.1
Commit: 8dfae7a5cd50421d10cd99cb873990460525a898
Date: 2022-04-06T14:51:26.173Z
Electron: 17.2.0
Chromium: 98.0.4758.109
Node.js: 16.13.0
V8: 9.8.177.11-electron.0
OS: Linux x64 5.13.0-39-generic
Front Matter: v7.1.1
**Describe the bug**
I am unable to properly phrase the issue, so please feel free to ask for details if I am missing anything. I have Front Matter set to open the dashboard automatically on startup of VSCode. Sometimes I close the dashboard tab before it is fully loaded. In that case, a bunch of errors pop up a little bit after that (see screenshots). I think whatever activity is running, should be "abandoned" when the tab is closed or issues with the "webview being disposed" should be caught. I do not have any additional or verbose debugging enabled, so I should not see the issues. It feels like there is some async stuff going on to populate the dashboard, that might be easily abandoned on tab-closure.
**To Reproduce**
Steps to reproduce the behavior:
1. Set dashboard to "open on startup"
2. start VSCode and close the dashboard tab right after it pops up
3. wait for it...
**Expected behavior**
No errors, catching the problem behind the scenes.
**Screenshots**



**VSCode:**
- Version: 1.66.1
- Commit: 8dfae7a5cd50421d10cd99cb873990460525a898
- Date: 2022-04-06T14:51:26.173Z
- Electron: 17.2.0
- Chromium: 98.0.4758.109
- Node.js: 16.13.0
- V8: 9.8.177.11-electron.0
- OS: Linux x64 5.13.0-39-generic
- Front Matter: v7.1.1
<!-- github-sync-id:1197363937 -->
That is indeed the background processing of the content. Will suppress these error notifications, as they are not required. Thanks!
That is indeed the background processing of the content. Will suppress these error notifications, as they are not required. Thanks!
<!-- github-comment-id:1094634929 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Describe the bug
I am unable to properly phrase the issue, so please feel free to ask for details if I am missing anything. I have Front Matter set to open the dashboard automatically on startup of VSCode. Sometimes I close the dashboard tab before it is fully loaded. In that case, a bunch of errors pop up a little bit after that (see screenshots). I think whatever activity is running, should be "abandoned" when the tab is closed or issues with the "webview being disposed" should be caught. I do not have any additional or verbose debugging enabled, so I should not see the issues. It feels like there is some async stuff going on to populate the dashboard, that might be easily abandoned on tab-closure.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No errors, catching the problem behind the scenes.
Screenshots
VSCode:
That is indeed the background processing of the content. Will suppress these error notifications, as they are not required. Thanks!