Browser Panel Causing Unbearable Lag

[tswwe]

What is the bug or the crash?

The problem is like what is described in this article. To be clear:

• When the browser panel is on, QGIS delays for a long time every several seconds. Basically unable to work.
• When the browser panel is turned off, QGIS becomes as fast as before.

Tested on 2 computers without network drivers. The problem occurs in QGIS 3.28.1 and doesn't occur in QGIS 3.22 LTR.

Steps to reproduce the issue

1. Freshly install QGIS 3.28.1 and launch
2. In the Browser Panel, navigate to a folder containing vector data

Versions

QGIS version
3.28.1-Firenze
QGIS code revision
fde3b8f
Qt version
5.15.3
Python version
3.9.5
GDAL/OGR version
3.6.0
PROJ version
9.1.0
EPSG Registry database version
v10.074 (2022-08-01)
GEOS version
3.11.1-CAPI-1.17.1
SQLite version
3.39.4
PDAL version
2.4.3
PostgreSQL client version
unknown
SpatiaLite version
5.0.1
QWT version
6.1.6
QScintilla2 version
2.13.1
OS version
Windows 10 Version 2009

Active Python plugins
db_manager
0.1.20
grassprovider
2.12.99
MetaSearch
0.3.6
processing
2.12.99
sagaprovider
2.12.99

Supported QGIS version

• I'm running a supported QGIS version according to the roadmap.

New profile

• I tried with a new QGIS profile

Additional context

No response

[kannes]

As it is, this is not an issue for others. Could you describe your environment more?

Does it happen in any browser containing any vector data?
Does it happen on other drives?
With other file formats?
Are you 100% sure your QGIS profile was a clean, default profile?
Does it happen if you disconnect your network connection completely?
Are you using a virus "protection" software (apart from Microsoft Defender)?

[github-actions]

The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale".
If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue.
In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue.
If there is no further activity on this issue, it will be closed in a week.

[github-actions]

While we hate to see this happen, this issue has been automatically closed because it has not had any activity in the last 42 days despite being marked as feedback. If this issue should be reconsidered, please follow the guidelines in the previous comment and reopen this issue.
Or, if you have any further questions, there are also further support channels that can help you.

[NickLanzer]

Was there any ever progress on this? I'm experiencing the same issue with 3.28 and 3.30.1. I've kept 3.26 alive since I literally cannot work in newer versions because of this issue.