An error dialog occasionally appears when attempting to open a blob container or file share
Storage Explorer Version
1.38.0 (105)
Regression From
Not a regression
Architecture
arm64
Storage Explorer Build Number
20250328.8
Platform
All
OS Version
Windows 11 arm64/Windows11 x64
Bug Description
An error dialog appears when attempting to open a file share, but the issue occurs inconsistently. So far, we have only encountered this problem on Windows platforms.
Steps to Reproduce
- Expand one storage account -> File Shares.
- Select one file share -> Open it.
- Check whether succeeds to open the file share.
Actual Experience
An error panel appears.
Expected Experience
Succeed to open the file share.
Additional Context
- We have encountered this issue several times in the past when opening both file shares & Blob Containers, but we have yet to identify a reliable method to reproduce it.
- Here are the App logs:
- Here is the record:
@v-xianya There are too many log files to really get a good read from them. When reproducing this issue, please try to keep the session small so the log files aren't so numerous.
The error appears to be getting thrown, because the code is trying to show an existing panel. Does this error ever occur just after launching Storage Explorer, or does it only happen after you've closed several file explorer tabs? My guess right now is the panel manager for file shares thinks a panel still exists and is trying to open it, but it is out of sync with the core app. If this is the case, I'm not yet sure how that might be happening.
@craxal We will attempt to share a brief log the next time we encounter this issue.
Does this error ever occur just after launching Storage Explorer, or does it only happen after you've closed several file explorer tabs?
This issue appears to occur after closing several Explorer tabs. We do not encounter this problem when initially opening an Explorer tab.
Haven't been able to reproduce on my end yet. I tried many times, different numbers of tabs.
There may be one lead we can follow. One of the renderer process log files does show an error getting thrown from the _finalizeClosedTabs() function. Functions don't finish executing when errors are thrown, so it's possible this error is interferring with clean up code. Fixing the error is easy, but I won't be able to verify without being able to reproduce.
Hi @craxal We met this issue on the main build 20250515.2.
Here is the app log, hope it helps😊
@v-xianya Sadly the logs don't reveal much. Have you encountered this recently? If it's happening only after a few tabs have been opened, I wonder if the session data is falling out of sync...
@craxal We haven't experienced this issue recently.
I'll close this as No Repro, then. If it does happen again, you can reopen.
We're getting several customer reports for this one, so I'm reopening the issue to investigate.
It seems most users encounter the issue when interacting with attached blob containers.