Hi Tobi,
i think safari did consume too much memory due to the number of placemarks (strikes) that have to be rendered into the map.
This exist on iPhone 5s with iOS 7.1.1 and iPhone 4 with iOS 6.1.3 too.
A possible solution temporalily solution could be, to render only strikes on the map, that are in the bounds of current view.
A second approach could be, to limit the time, that a strike is placed on the map.
-NosDE
i think safari did consume too much memory due to the number of placemarks (strikes) that have to be rendered into the map.
This exist on iPhone 5s with iOS 7.1.1 and iPhone 4 with iOS 6.1.3 too.
A possible solution temporalily solution could be, to render only strikes on the map, that are in the bounds of current view.
A second approach could be, to limit the time, that a strike is placed on the map.
-NosDE