Bug report #7420
"sum line lenghts" never ends (freezes qgis)/memory leak
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Severe/Regression | ||
| Assignee: | - | ||
| Category: | Processing/QGIS | ||
| Affected QGIS version: | master | Regression?: | |
| Operating System: | Easy fix?: | ||
| Pull Request or Patch supplied: | No | Resolution: | fixed |
| Crashes QGIS or corrupts data: | Yes | Copied to github as #: | 16383 |
Description
With the attached vectors, if the line one is PostGIS, the tool "sum line lenghts" freezes qgis. Tested master with Windows.
It seems to work if both vectors are shapefiles.
History
#1
Updated by vinayan Parameswaran over 11 years ago
I had this problem when running this tool(Ubuntu) just after you reported(even when two shapefiles were used). Memory usage was at a high. But today everything seems good. There was an issue with the progress bar showing incorrect progress which should be addressed in #7964.
Could you check it once again(just ignore the progress bar)?
#2
Updated by Giovanni Manghi over 11 years ago
- Subject changed from "sum line lenghts" never ends (freezes qgis) to "sum line lenghts" never ends (freezes qgis)/memory leak
vinayan Parameswaran wrote:
I had this problem when running this tool(Ubuntu) just after you reported(even when two shapefiles were used). Memory usage was at a high. But today everything seems good. There was an issue with the progress bar showing incorrect progress which should be addressed in #7964.
Could you check it once again(just ignore the progress bar)?
Hi,
I just update on win/osgeo4w and tested the operation with the two attached shapes.
It doesn't work and now it seems there is a memory leak. The operation reach 48%, then qgis starts eating up memory and eventually finishes correctly. If the inputs are bigger then would lead to crash.
I already reported that there is also a (new) memory leak in the clip tool.
#3
Updated by Giovanni Manghi over 11 years ago
vinayan Parameswaran wrote:
I had this problem when running this tool(Ubuntu) just after you reported(even when two shapefiles were used). Memory usage was at a high. But today everything seems good. There was an issue with the progress bar showing incorrect progress which should be addressed in #7964.
Could you check it once again(just ignore the progress bar)?
and I see now that memory is not released after the operation.
#4
Updated by vinayan Parameswaran over 11 years ago
I had the same issue(memory not released) a few weeks ago..the current master build on ubuntu does not seem to have it..qgis always staying under 100mb memory..
#5
Updated by Giovanni Manghi over 11 years ago
- Status changed from Open to Feedback
vinayan Parameswaran wrote:
I had the same issue(memory not released) a few weeks ago..the current master build on ubuntu does not seem to have it..qgis always staying under 100mb memory..
will test also on Linux, but on Windows/osgeo4w (latest build) seems still an issue.
#6
Updated by Giovanni Manghi over 11 years ago
vinayan Parameswaran wrote:
I had the same issue(memory not released) a few weeks ago..the current master build on ubuntu does not seem to have it..qgis always staying under 100mb memory..
just tested on Linux/Ubuntu on a build dated 29 May, with the attached vectors and I still see the leak. The operation takes gradually 1gb of memory. Tested with bigger datasets it leads to crash.
#7
Updated by Giovanni Manghi over 11 years ago
- Status changed from Feedback to Open
#8
Updated by Giovanni Manghi over 11 years ago
- Status changed from Open to Closed
- Resolution set to fixed
#9
Updated by Giovanni Manghi over 7 years ago
The "ftools" category is being removed from the tracker, changing the category of this ticket to "Processing/QGIS" to not leave the category orphaned.