It has now a problem without codesets.library and it introduced new graphical problem.
I haven't touched the non-codesets code so that must be caused by something else.
Probably where the code is now offset differently the old bug causing it to access memory it shouldn't be is having a different effect.
This hasn't answered the question I wanted answered which was "is it any quicker now *with codesets.library*?"
Would it be possible to revert back few years old version so that new amissl would work with it? Those versions were almost usefull, these versions.. it doesn't matter if you fix or not these problems, there is no point to use it as it loads page like amigaworld.net about 5 minits. It used to load about 15 seconds, when Olaf fixed memory fragmentation issue three? years ago.
I have no idea what caused it to go slow as I was told about this several months after it happened. I have absolutely no chance of figuring out why now as I couldn't even at the time.
The memory model hasn't changed since then.
It's probably worth adding log_filter:level:CRITICAL to Choices because by default it is spewing out loads of Javascript-related errors which will be slowing it down.
I did switch to using AmiSSL as OpenSSL stopped working, I can't revert that change as not being able to make secure connections makes the browser useless. There's no reason why AmiSSL should be slower than OpenSSL anyway, it's 99% the same thing.
What it needs is for somebody who can actually debug it properly to figure out what is causing the suspected buffer overflow problem and fix that. That gets rid of the weirdness of it randomly crashing and doing odd things. Then it's worth spending a bit of time optimising (again, by somebody who knows what they are doing).
