I'm creating an application that uses a floor plan (an exported CAD drawing to XAML.) The floor plan is approximately 1.4 megabytes big in text that has a canvas object and several thousand paths. I download it using the download object and I render it with CreateFromXaml. It works for a while, but once I start fooling with the scale or translate transforms, Microsoft Internet Explorer suddenly jumps to near 100% CPU usage cycles and crashes.
The thing is that this application works with smaller less detailed floor plans with no problems whatsoever. Is there an upper limit to the number of things that Silverlight can handle before it bombs with a memory leak?
Performance issues is one thing, I think this is a memory leak because Internet Explorer starts taking up processor cycles (upwards to 98%) and needs to be terminated.
I think I may have isolated the problem.
I use thousands of Path objects that I exported from a CAD to XAML. The export contains the following tags that seem to take up huge amounts of memory to render, resize and transform:
It seems when I removed those tags, Silverlight's performance improved and the memory leak stopped.