I'm not sure about the fact I followed the discussion (I've read so many things that I don't remember why ! ^^), but that's right ! AmiKit sometimes rebooted all alone while I was using NetSurf.
amiga system doesnt have memory protection, therefore a faulty application may reproducibly bring the whole system down or effectively reboot it. in many cases at least the faulty memory allocations, reads and writes may be intercepted by a third party software. for systems with mmu the muforce package from aminet.net is advisable. you can enable mmu in your uae settings or even use uaeenfircer directly, typing "winuaeenforcer" command into your amiga shell under uae.
there has been discussion about the choice of c library to be linked against and therefore memory allocator associated with this library. i would have to look for a link. basically you can link against clib2 as its default with netsurf, which is initially faster but appears to slow down dramatically pretty soon. then you can usually link with the libnix option, and as less encouraged, you can take advantage of one of the ixemul library versions, latest of which use internally some buddy allocator. also there is external implementation of tlsf fir amiga, rather rarely used and probably also not well tested due to (expected) incompatibilities. however im not sure what compiler and build config you use. is it some form of amidevcpp?
im sorry for this lengthy post, and things you may be aware of, but you seem to be new here, so i may be mentioning platitudes.
I'm sorry, I didn't understand what you wanted to say here. Do you mean AmiKit is made with Java ?
i think he would prefer you to fix the browser itself, before trying to implement javascript engine. this is what ducktape is, for what i recall?
