Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Application hangs indefinitey when closing project with GeoPakages shared on network drive. Cannot kill process. Requires shutdown/restart. #26333

Closed
qgib opened this issue Mar 14, 2018 · 5 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption Data Provider Related to specific vector, raster or mesh data providers High Priority

Comments

@qgib
Copy link
Contributor

qgib commented Mar 14, 2018

Author Name: Graham Duls (Graham Duls)
Original Redmine Issue: 18445
Affected QGIS version: 3.0.0
Redmine category:data_provider


For a few years we have had one computer keep a QGIS project and related layer files in a folder on a network directory and we all open that project. After upgrading to QGIS3 someone re-saved many layers as GeoPackages (they were formerly zipped shapefiles). After having the project open for a while (and it is running just fine, by the way) when attempting to close the application, QGIS become non-responsive and it cannot be closed by the task manager (I also tried a couple 3rd party apps such as TaskKiller). The computer must be shut down or restarted. Re-opening the project reveals one (or more) GeoPackage layers are invalid and they cannot be deleted unless another project is loaded into QGIS. Note that all layers in the project are set to read-only and no editing is ever done. Saving is done if styles are changed.
The host computer is Windows10 64bit - satellites are: Another Windows10 64bit, a Windows10 32bit, and a Windows7 (can't remember, I think 32bit.) Note that the Windows7 computer never has this problem and QGIS closes just fine for that machine (so far).

@qgib
Copy link
Contributor Author

qgib commented Nov 8, 2018

Author Name: Giovanni Manghi (@gioman)


Please try on QGIS 3.4.1, if the issue is still valid change the affected version, thanks.


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Dec 3, 2018

Author Name: Graham Duls (Graham Duls)


I will try to reproduce the conditions that caused this issue. Please give me time, as we are not fans of corrupted data, or locked computers. We have moved on to different, more stable, methods, but I can attempt to reproduce this problem and will post here.

@qgib
Copy link
Contributor Author

qgib commented Dec 5, 2018

Author Name: Giovanni Manghi (@gioman)


Graham Duls wrote:

I will try to reproduce the conditions that caused this issue. Please give me time, as we are not fans of corrupted data, or locked computers. We have moved on to different, more stable, methods, but I can attempt to reproduce this problem and will post here.

at some point without feedback this will be closed, if the issue is confirmed you will be able to reopen it if necessary.

@qgib
Copy link
Contributor Author

qgib commented Dec 5, 2018

Author Name: Graham Duls (Graham Duls)


I am unable to reproduce the issue. Feel free to close this.

@qgib
Copy link
Contributor Author

qgib commented Dec 6, 2018

Author Name: Giovanni Manghi (@gioman)


  • resolution was changed from to not reproducable
  • status_id was changed from Feedback to Closed

@qgib qgib closed this as completed Dec 6, 2018
@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! High Priority Data Provider Related to specific vector, raster or mesh data providers Crash/Data Corruption labels May 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption Data Provider Related to specific vector, raster or mesh data providers High Priority
Projects
None yet
Development

No branches or pull requests

1 participant