https://issues.qgis.org/https://issues.qgis.org/favicon.ico2019-03-15T18:06:20ZQGIS Issue TrackingQGIS Application - Bug report #21596: Editing a memory layer is corrupted when recreating a memory layer with same namehttps://issues.qgis.org/issues/21596?journal_id=1031432019-03-15T18:06:20ZVincent Dionne
<ul></ul><p>BTW, the name of the second memory layer can be different... and you will get the same result.</p> QGIS Application - Bug report #21596: Editing a memory layer is corrupted when recreating a memory layer with same namehttps://issues.qgis.org/issues/21596?journal_id=1031482019-03-16T06:13:30ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Feedback</i></li></ul><p>Cannot replicate here. Have you tried with a new/clean profile (no 3rd party plugins)?</p> QGIS Application - Bug report #21596: Editing a memory layer is corrupted when recreating a memory layer with same namehttps://issues.qgis.org/issues/21596?journal_id=1033182019-03-21T15:59:34ZAlessandro Pasotti
<ul><li><strong>Affected QGIS version</strong> changed from <i>3.6.0</i> to <i>3.7(master)</i></li><li><strong>Assignee</strong> set to <i>Alessandro Pasotti</i></li></ul><p>I've been able to reproduce a similar bug on a different workflow.<br />I'm still struggling to reproduce it in a test but I'm working on it.</p> QGIS Application - Bug report #21596: Editing a memory layer is corrupted when recreating a memory layer with same namehttps://issues.qgis.org/issues/21596?journal_id=1033192019-03-21T17:38:42ZAlessandro Pasotti
<ul><li><strong>Assignee</strong> deleted (<del><i>Alessandro Pasotti</i></del>)</li></ul><p>No, sorry: it was a different problem and I could not reproduce the issue described in this ticket.</p>
<p>The only way to reproduce a similar issue is if you delete the features directly from the provder without passing through the QgsVectorLayer edit buffer, which is not recommended btw.</p>
<p>If you remove the layer from the legend it gets deleted and if it gets deleted the snapping locator cache is cleared (well, not really cleared but it won't get used for another layer even if it has the same name).</p>