>
> #sizeInMemory only takes into account object header size and the size of the
> object
> itself.
>
> sizeInMemory is also ignorant of details such as the padding of objects to
> 64-bits in both 32-bit and 64-bit Spur, the overflow header when there are
> more than 254 slots, etc.
Hi Marcus,
On Thu, Oct 26, 2017 at 1:09 AM, Marcus Denker
wrote:
>
>
> On 26 Oct 2017, at 10:05, Denis Kudriashov wrote:
>
> Hi.
>
> Question from discord, why:
>
> 2017 sizeInMemory = 0
>
> ?
>
> Looks like a bug, but maybe there is some reason
Because it is an immediate value.
On 26 Oct 2017 10:06, "Denis Kudriashov" wrote:
Hi.
Question from discord, why:
2017 sizeInMemory = 0
?
Looks like a bug, but maybe there is some reason for this.
> On 26 Oct 2017, at 10:05, Denis Kudriashov wrote:
>
> Hi.
>
> Question from discord, why:
>
> 2017 sizeInMemory = 0
>
> ?
>
> Looks like a bug, but maybe there is some reason for this.
#sizeInMemory only takes into account object header size and the size of the
Hi.
Question from discord, why:
2017 sizeInMemory = 0
?
Looks like a bug, but maybe there is some reason for this.