Oh! I forgot this fact!

The O3D plugin *includes* the lightning quick V8 javascript engine built in, so the total memory consumption at start is an impressively reasonable 30MB! It should also considerably ease the integration of o3d in a stand-alone player as binding a JS engine will not be required.

This choice was chosen to improve performance in browsers with slow or non-compliant javascript engines (*cough* IE *cough*). V8 is a POWERHOUSE engine that's extremely fast despite being dynamically typed. I think it was a very smart design decision on the O3D teams part (as were many O3D choices).

Out of interest, does anyone know how much memory the N900 browser consumes on a blank page?

}:^D~