#2814: digitizer crashes, leaves vector broken --------------------------+------------------------------- Reporter: harrikoo | Owner: grass-dev@… Type: defect | Status: new Priority: critical | Milestone: 7.0.3 Component: wxGUI | Version: 7.0.2 Resolution: | Keywords: digitizer, vector CPU: Unspecified | Platform: Unspecified --------------------------+-------------------------------
Comment (by mlennert): Replying to [comment:22 harrikoo]: > Replying to [comment:20 martinl]: > > Replying to [comment:18 harrikoo]: > > > Now it just happened again! I was drawing a test vector and crossing lines and boundaries, breaking them and merging them, and then in the end, deleting extra lines; immediately after the deletion of one line (select with left, confirm with right) the digitizer crashed. This was not the first line I deleted, perhaps the 20th, so it was something particular about that line. > > > > Please try to write down step-by-step instructions (or video showing all operations) which could help us to reproduce the issue as much easy as possible. Thanks. > > Another one: Drawing lots of areas, crossing each other, changing lines/boundaries etc. In the end a crash, when I was moving the first/last vertex of a loose boundary line to another place. No intersections took place here. If areas were crossing each other, how can there have been no intersections ? > > Since in each case it always takes a lot of drawing to cause the bug, perhaps the bug has something to do with the amount of drawing operations? I haven't experienced this that much in my daily work lately, since I usually digitize only a few areas or lines at a time and then save the map. Could this be something that manifests after a certain amount of operations? Will have to begin counting the operations when I next have time to work on this one. I've really tried to reproduce, digitizing many areas and lines, crossing each other or not, changing line types, undoing, redoing, etc. I cannot reproduce. On what OS are you ? As Martin said, a video would be very helpful in understanding the kind of situation where this happens. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/2814#comment:23> GRASS GIS <https://grass.osgeo.org> _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev