K-Meleon :: General

General : K-Meleon Forum

General discussion about K-Meleon.

Goto: Forum List•Message List•Search•Log In

Your Name:
Subject:

Help information

[quote=snuz2]
yeah, they don't retrofit that unless it comes by accident. but there were 2 big jumps in speed in FF, one was v4 and one was earlier, and in between they kept ramping up the speed in the intermediate versions. I was thinking of the js engine in the Fred's 1.7 hybrid, which is almost like FF4. but that may not be in either of the builds I compared, i don't remember.

My main point is that builds that don't have the random mouse selection bug also run faster. whether that is because they were built for speed rather than size, or it is just a side effect of different compilation options or library versions, I don't know. 
But a bug that 
 - exists in 1.6B2, but not one of Fred's builds, and then reappears in his later builds
 - has to do with handling input/output, and seems to generally slow the execution
doesn't seem like an error in KM code itself. It seems like a build configuration problem. i don't think it is a direct result of compiling for speed/ size itself but maybe a library changes when that or some other option is selected and something doesn't work right anymore. could just be my imagination.

maybe selecting compact size activates some memory scavenging mechanism that causes input to be dropped and random pauses, but i doubt it.

anyway, builds that don't have the random mouse select bug seem to run much better in general on my machine and i think that that bug is a symptom of a larger performance killing problem. builds without the bug also seem to respond to user input faster and more consistently. that's the point i'm trying to make.[/quote]

K-Meleon forum is powered by Phorum.