First of all, it's important to distinguish program crashes and errors when describing your situation
- a program crash is an event where an application closes or freezes without telling you a reason (this is always a program bug and must be fixed by the developers)
- a program error is an event where the application stops working but gives you a reason (i.e. invalid route, unknown something or other). This is almost always caused by invalid use and can be fixed by the user
It seems that you encountered an error (whereas editing a .net.xml file manually would have been one of the few ways for a user to cause a crash).
Whenever you modify the network with netedit, it may cause some of the old traffic demand to become invalid so you need to rebuild it. Likeways, if you are using routes that were build for an old network, vehicles may never use your new roads. (it depends on whether you are loading <vehicle> or <trip> definitions).
From your screenshot it looks as if the new road isn't connected with the rest of the network (no T-intersection shape is visible). You must split the horizontal road (
https://sumo.dlr.de/docs/Netedit/neteditPopupFunctions.html#edge_and_lane) to create a new junction and attach your new road to that junction (i.e. move them onto the same spot and confirm "merge").
In order for routeSampler to generate some traffic that passes from your new road into the larger network you need to make sure that the input contains such routes. The following may help
- rerun randomTrips.py (or build.bat) on the new network and increase the amount of traffic (i.e. higher end time)
- add routeSamper.py option --min-count 2 to prevent short routes which only pass a single detector
regards,
Jakob