Lots of hangs in the 4.1.1 simulator with the Memory view open

Although its not mentioned in the release notes (or I've missed it) sdk4.1.2 seems to have made things much better. With my app, when I open the memory window, there's no noticeable slowdown and no beach-ball cursor. I can even selectively expand some of the fields, and everything continues to work. But expand all still locks things up and I have to force-quit the simulator.

I've spent some time trying to figure out what it is about my app thats causing the problem, and discovered that if I rip out all of the settings/properties and associated strings, things get much better. I can open the memory window, and cpu usage "only" goes up to around 80%, instead of maxing out and becoming unresponsive. If I then "expand all", it hits 100%, and starts hanging again; but prior to those changes, I didn't need the expand all step.

So I tried taking all those resources, and just adding them to the SimpleDataField sample. Without those changes, cpu sits at around 30% with no memory window, 40% with the memory window open, and 50% with expand all. After adding my resources, it hits 75% when I open the memory window, and starts hanging when I do expand all.

Here's the patch I applied to SimpleDataField: gist.github.com/.../eacfbbb5b519b2d5be8e37fde5bcb0ad

Thanks Brandon, my MAC (the details of which you've reposted here from the other thread) is an intel mac (not an M1)

Also, I've just tried the same project on my somewhat dated windows 10 machine (from 2015). No problems at all.

macos monerery 12.2.1, macbook pro 2019 (intel). Its a datafield, and when I have the memory window open, it only updates every few seconds, and the cursor is a spinner most of the time. I tried a few of the sample apps, and it didn't repro. I just attempted to post this with a screen capture video, but it looks like my reply was just discarded (the video was probably too big).