I might be wrong but clarify this... The problem aki has mentioned sounds like a memory leak and not really the size of the class object. I dont think you can practically write an object that consumes GB's of memory :) Anyway. If I am right and its a memory leak then you have some object thats getting called often and is not being deleted. Eg in a for loop or something. Or an exception of some sort is is causing the break out of a function before the object is deleted. or maybe you can clearly state what exactly the problem is ----- Original Message ----- | From: "James Nzomo" <kazikubwa@gmail.com> | To: "Skunkworks Mailing List" <skunkworks@lists.my.co.ke> | Sent: Monday, November 28, 2011 12:16:21 PM | Subject: Re: [Skunkworks] Size of an object in memory at runtime | Thank you aki, that was a very helpful insight (really). | Are there any C++ 1337s on the list who have encountered this problem | and solved it? | I am trying to avoid painstaking workarounds such as adding up the | size of each member or using JSON. | Anyone? | _______________________________________________ | Good judgement comes from Experience. | Most of that comes from Bad Judgement. | _______________________________________________ | 2011/11/28 aki < aki275@gmail.com > | _______________________________________________ | Skunkworks mailing list | Skunkworks@lists.my.co.ke