I had uncompressed data in mind, but it was only a rough guess. I'll do a more in depth calculation.
2 seconds of uncompressed sound, at 44.1 kHz, in stereo and 8 bits per sample is 170 KiB. 17 images of on average 24 by 24 pixels at 32 bits per pixel is 68 KiB. Three other, bigger images give another 40 KiB of uncompressed data. A total ~280 KiB. There's a few KiB of HTML but I don't know whether and how I should count that. Even if we take into account headers, padding, objects and higher quality data (e.g. 16 bits per sample), I assume all assets will still account for less than half a megabyte.
Now that I look at the code, I see it's including a bundled version of jQuery. I don't know how big the representation of Javascript code is in memory, but 29 MiB seems a bit much (correction, while I was typing this, it went to 31 MiB).
It might seems disingenuous to single out this extensions, but truth to be told all my extensions need a similar, way too high amount of private memory.
Neither, as I am only looking at private memory, which is by definition not shared. Interestingly, most of my extensions have 0K shared memory, which implies they're all keeping their own version of JavaScript libraries in their own memory space. That might explain most of the problem. It doesn't seem easy to solve a problem like this, without reinventing the shared library and the accompanying "DLL hell".
2 seconds of uncompressed sound, at 44.1 kHz, in stereo and 8 bits per sample is 170 KiB. 17 images of on average 24 by 24 pixels at 32 bits per pixel is 68 KiB. Three other, bigger images give another 40 KiB of uncompressed data. A total ~280 KiB. There's a few KiB of HTML but I don't know whether and how I should count that. Even if we take into account headers, padding, objects and higher quality data (e.g. 16 bits per sample), I assume all assets will still account for less than half a megabyte.
Now that I look at the code, I see it's including a bundled version of jQuery. I don't know how big the representation of Javascript code is in memory, but 29 MiB seems a bit much (correction, while I was typing this, it went to 31 MiB).
It might seems disingenuous to single out this extensions, but truth to be told all my extensions need a similar, way too high amount of private memory.