<JOKE>In summary: Manfred's answer is that you can't, and my answer is that you don't want to.</JOKE> It's too painful. I can feel my shoulders sag sometimes when I think about how each say simple 32-bits in-theory number is blowing out under the hood to many multiples of that in size.Is there a simple way to determine the memory usage of an Object?
Thx will do.Sounds like a preoptimization. Start with the simplest implementation and see if it works good enough. In most cases it will.
I thought I saw 1000 objects ~ 1.6 GB.I was quite surprised to find that the individual Blob fields are only about 1K each.
Thx, I'll check those out.Two examples that demonstrate how you can show any number of images:
1. With B4XTable: https://www.b4x.com/android/forum/threads/b4xtable-photos-album.103343/#content
2. With xCustomListView: https://www.b4x.com/android/forum/t...r-columns-of-imageviews-and-many-rows.101431/
Yes, chrome is an insane memory hog. I'm sure of my current 5GB usage Chrome is about 4GB of them.I thought I saw 1000 objects ~ 1.6 GB.
Speaking of memory (ab)use, I looked up a local bus timetable on the web today, everything went slow, and I eventually found that Chrome was using 520 MB (YES, OVER HALF A GIG) to display ONE text-only web page. Wtf?