We are currently experiencing a weird issue when having WWW draw SVGs as placemarks. Previously we had one regular SVG element that contained paths in it. To optimize some things we merged a few SVGs together using valid syntax of an SVG inside of another SVG element. But when we did this we observed horrible memory performance when WWW would try and draw more than 2000 placemarks with these merged SVGs, to the point where the memory consumption gets so much chrome crashes.
Is there anything from a WebGL perspective that could cause this? Or maybe in WWW code? We have started digging through the WWW code but haven't found anything yet.
Is there anything from a WebGL perspective that could cause this? Or maybe in WWW code? We have started digging through the WWW code but haven't found anything yet.
Comment