You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Information tab inside the properties window of a WMS layer shows the full list of layers parsed from the GetCapabilities document when the layer is loaded.
This is problematic when the WMS service includes hundreds or thousands of layers. QGIS freezes or crashes when the Information tab is clicked.
In my opinion, the "Other layers" section under "Information from Provider" is not required and should be removed, since the layer's properties window is related to the single layer, not the origin WMS service.
Open the layer's dialog and navigate to the Information tab,
Versions
Tested on QGIS 3.34 and 3.40
Supported QGIS version
I'm running a supported QGIS version according to the roadmap.
The text was updated successfully, but these errors were encountered:
giohappy
added
the
Bug
Either a bug report, or a bug fix. Let's hope for the latter!
label
Nov 28, 2024
giohappy
changed the title
WMS layer's properties window freezes when the origin WMS service's GetCapabilities document contains thousands of layers
WMS layer properties window freezes when the origin the GetCapabilities document of the origin sever contains thousands of layers
Nov 28, 2024
What is the bug or the crash?
The Information tab inside the properties window of a WMS layer shows the full list of layers parsed from the GetCapabilities document when the layer is loaded.
This is problematic when the WMS service includes hundreds or thousands of layers. QGIS freezes or crashes when the Information tab is clicked.
In my opinion, the "Other layers" section under "Information from Provider" is not required and should be removed, since the layer's properties window is related to the single layer, not the origin WMS service.
Steps to reproduce the issue
Versions
Tested on QGIS 3.34 and 3.40
Supported QGIS version
The text was updated successfully, but these errors were encountered: