"sum line lenghts" never ends (freezes qgis)/memory leak

[qgib]

Author Name: Giovanni Manghi (@gioman)
Original Redmine Issue: 7420
Affected QGIS version: master
Redmine category:processing/qgis

---

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.

---

• attach.zip (Giovanni Manghi)

[qgib]

Author Name: vinayan Parameswaran (vinayan Parameswaran)

---

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 #16823.

Could you check it once again(just ignore the progress bar)?

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

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 #16823.

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.

---

• subject was changed from "sum line lenghts" never ends (freezes qgis) to "sum line lenghts" never ends (freezes qgis)/memory leak

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

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 #16823.

Could you check it once again(just ignore the progress bar)?

and I see now that memory is not released after the operation.

[qgib]

Author Name: vinayan Parameswaran (vinayan Parameswaran)

---

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..

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

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.

---

• status_id was changed from Open to Feedback

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

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.

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

• status_id was changed from Feedback to Open

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

• status_id was changed from Open to Closed
• resolution was changed from to fixed

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

The "ftools" category is being removed from the tracker, changing the category of this ticket to "Processing/QGIS" to not leave the category orphaned.