Hi
I’ve got a relatively large System.Byte[ ] section in the memory profiler result. It is 230MB, approx 50% of all memory used by my app.
How can one find out what it is?
1 Like
Looking at the content byte by byte is likely going to be tough to parse. It still being in memory means there’s a likely chance something still holds a reference to it. If that’s the case the Ref Count column should hold a blue number. Clicking on that would show you a list of Objects that reference it (each with a Ref Count of their own). Following that trail is likely to be your best chance of figuring out what’s up with that byte array.
You could also search your codebase for byte[ or similar but it might be a return value stored in a var, so… that might lead nowhere.
Interesting, I have 5541 of these taking up 4.74gig of ram. I cant work out how to track objects that use these arrays, I just see managed fields, with a list of arrays, I do see referenced by but it all seems to be related to the memory profiler itself. Also theres many many references in some cases 75k (is that using more memory needlessly?), just wondering how I track this down given that it doesnt seem to show me the objects using/creating them. I dont see any blue numbers.
2 Likes