Closed Despert1 closed 2 years ago
@Despert1 please add/attach the raster you want to georef, the gcp table and georef parameters.
I've do it but same problem. I use Qgis since 8 years ant when a use georferencer I've the same method. It' the first time that my comuter freezes.
@Despert1 please add/attach the raster you want to georef, the gcp table and georef parameters.
I have this happen to my user profile eventually and have to create a new profile to get the georeferencer to work again. I cannot determine why the georeferencer becomes corrupted in the user profile and hangs when starting the georeference transformation. A new profile is a certain fix but can be time consuming when needing to reinstall and configure a suite of plugins.
LTR 3.16
I have this happen to my user profile eventually and have to create a new profile to get the georeferencer to work again. I cannot determine why the georeferencer becomes corrupted in the user profile and hangs when starting the georeference transformation. A new profile is a certain fix but can be time consuming when needing to reinstall and configure a suite of plugins.
LTR 3.16
Thank you so much for this! I just backed-up my profile folder, wiped it out, and tried my failed georeference again... And it worked lika a charm! Then I started digging into what was the problem, copying back files from my backup, and it turned out it was QGIS3.ini
. After some further investigation of my settings I found out that for me the culprit was this specific line of a [SemiAutomaticClassificationPlugin] block: threadsValue=4
. If it's set to anything other than 1
the georeferencer freezes. Have no idea how this line of a plugin can impact the georeferencer but it seems like it happens on startup, since when I set "threadsValue" via the plugin's GUI georeferencing seem to work until I restart QGIS. (3.22.1 Bialowieza, btw)
And if I deactivate the plugin, even when the .ini file has the parameter set to 4, the georeferencer works normally. The plugin's initialisation routine messes things up...? This is supported by the fact that if I start QGIS with the plugin deactivated I can georeference w/o problems, however if I then go and activate the plugin the next georeferencing then freezes. And just for "scientific" exhaustiveness: if I start QGIS with the plugin activated (and threadsValue
set to 4) and then disable it before georeferencing, it still freezes.
[SemiAutomaticClassificationPlugin]
@RinceWND this is why we always ask to check/test with a new QGIS profile and no 3rd party plugins installed.
For now, temporarly disable the SACP, if you have it installed, before doing a georeferencing session.
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.
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.
I have this happen to my user profile eventually and have to create a new profile to get the georeferencer to work again. I cannot determine why the georeferencer becomes corrupted in the user profile and hangs when starting the georeference transformation. A new profile is a certain fix but can be time consuming when needing to reinstall and configure a suite of plugins. LTR 3.16
Thank you so much for this! I just backed-up my profile folder, wiped it out, and tried my failed georeference again... And it worked lika a charm! Then I started digging into what was the problem, copying back files from my backup, and it turned out it was
QGIS3.ini
. After some further investigation of my settings I found out that for me the culprit was this specific line of a [SemiAutomaticClassificationPlugin] block:threadsValue=4
. If it's set to anything other than1
the georeferencer freezes. Have no idea how this line of a plugin can impact the georeferencer but it seems like it happens on startup, since when I set "threadsValue" via the plugin's GUI georeferencing seem to work until I restart QGIS. (3.22.1 Bialowieza, btw)And if I deactivate the plugin, even when the .ini file has the parameter set to 4, the georeferencer works normally. The plugin's initialisation routine messes things up...? This is supported by the fact that if I start QGIS with the plugin deactivated I can georeference w/o problems, however if I then go and activate the plugin the next georeferencing then freezes. And just for "scientific" exhaustiveness: if I start QGIS with the plugin activated (and
threadsValue
set to 4) and then disable it before georeferencing, it still freezes.
Amazing tips ! It's working perfectly
threadsValue=1 also worked for me, thanks @RinceWND ! I would really love to understand what the underlying issue might be, and was it fixed in any newer version? (I am using the stable version 3.22.6-Białowieża)
What is the bug or the crash?
Each time I run the calculation linked to the georeferencer, it freezes for the computer. I can place my points, and choose the parameters but after the program freezes. I uninstalled and reinstalled QGIS (Hannover) but without success the problem persists.
Steps to reproduce the issue
Versions
I am using both Hanover and version 3.22.1
Supported QGIS version
New profile
Additional context
No response