layer properties dialog takes >30 seconds to show up for vector layers when qgis profile folder is on network drive #37899
Comments
beerockxs
added
the
Bug
|
might be the same issue as #34942 ? Can you please check if this is the case? If yes, then this is solved in the nightly. |
|
This happens with a project that has only the single layer, so I don't believe it's #34942 |
|
This applies to shapefile layers as well, for raster layers, the delay is < 1 sec |
|
I also tried using the current nightly from OSGEO4W, and it still happens.
|
|
@beerockxs just to be sure... try with a new QGIS profile. |
|
As I said in the initial report, I did create a new profile. With QGIS 3.10, it takes also less than 1 second. |
beerockxs
changed the title
sorry I overlooked that. |
|
Does this also happen if you try with a shapefile located on a local folder and not on a mapped drive or over the network? Could be windows networking issues. |
|
It also happens with local shapefiles. |
|
The master shown was post-fix regarding the mask loading. There is something else at play. |
|
I can confirm the same: properties dialog on a single layer from geopackage file takes ~10 seconds to open on QGIS 3.14.1 Version details:
|
gioman
added
Vectors
|
Is there anything I as a user can do to help find the cause for this? |
@beerockxs hard to say, seems a local issue. Have you tried on a different machine? |
|
Further debugging reveals that this is tied to the location of the qgis profile folder. When I move it out of my windows profile folder, which is on a networked folder, the dialog pops up in ca. 1.5 seconds. |
beerockxs
changed the title
|
Why is your profile folder on a network folder and not locally? |
|
Corporate environment with roaming profiles probably |
|
Exactly |
|
If you want to have a crack at possibly debugging this. There is a tool
called Procmon. It's quite handy to show timings for how long each
operation takes like reading files, etc, it might be loading a lot of small
files or something which is slowing something down. I can put together
some notes on how to use it if you haven't used it before.
…On Wed, Sep 2, 2020 at 9:12 PM Sebastian Brocks ***@***.***> wrote:
Further debugging revels that this is tied to the location of the qgis
profile folder. When I move it out of my windows profile folder, which is
on a networked folder, the dialog pops up in ca. 1.5 seconds.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#37899 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAC5FXDWU7UWCD7JWLRL46DSDYSADANCNFSM4PDTPJ4Q>
.
|
|
I'll gladly look into that, some pointers on how to use it would be great. |
|
I looked into this a bit, there are a few operations that happen multiple times and take quite long, like these: 09:49:24,8723953 qgis-dev-bin-g7.exe 17640 CreateFile \bamdefm-fsv01.prod.bam.nl...designer\backup.designer\xpm\new_attribute.png BAD NETWORK NAME Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: N, ShareMode: Read, Write, AllocationSize: n/a |
|
Hello @beerockxs I've tested this issue on QGIS 3.22.3. and I'm not being able to reproduce it. Did you come across this issue more recently? |
|
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". |
github-actions
bot
added
the
stale
|
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. |
Using QGIS 3.14 on windows with a fresh user profile and no non-core plugins installed, the layer properties dialog takes >30 seconds to appear after clicking on it. Using the same database with QGIS 2.18, it takes about 1 second.
The text was updated successfully, but these errors were encountered: