Call it by any numbering scheme, as long as its updated to current level, that is what truly matters & what I must thank Dorian & team for their patient work,and Fred, Gunter and others for their unpaid support.

I salute all of you and thank you from bottom of my heart for giving us this great browser for Windows (for Linux- thanks Fred ! Thanks Hao for CCME)

Hallo,
As far as i can see the only upgrade from the 1.1.5 to 1.1.6 is the GRE, the readme.html and the general.useragent.vendorSub value.
Is this correct? (not a criticism, just to know if makes sense for me to upgrade since i made a little script to automaticly daily update the gre with the latest seamonkey 1.8 nightly.)

@sufi - check the status of your Cookies - Edit-Preferences-Privacy to make sure that they are set to "Always". I believe that 1.5 comes defaulted to "From the Originating Website". Not allowing Cookies on some sites sometimes gives you the message that the browser cannot connect.

The problem is SHIFT key, this isn't recognized when you use it in accelerators with NUMPAD keys. If you try with CTRL only, ALT only or CTR+ALT combination, works fine.
This must be a bug. This problem happend in 1.1.X and 1.5RC.

Thanks for that info about SHIFT key. I don't think it is a bug. I should have realized that you cannot shift key in the number pad. The change of operation for those keys is handled by the NUMS LOCK key.

I'm using K-Meleon 1.1.6 and noticing slightly increasing memory usage. It was in previous version 5 too and now is even more. K-Meleon is not freeing occupied memory and after some time it looks like it's trying to challening ff2 in "Who will eat more memory" contest.

Now one tab and it does occupy 75MB, minimize, restore and it will be only 14MB. Having more tabs (layouts actually in K-Meleon terminology) the trick is loosing its grip and smooth the most crucial difference between K-Meleon and firefox. (But why is needed at all?)

QuotezelgonI'm using K-Meleon 1.1.6 and noticing slightly increasing memory usage. It was in previous version 5 too and now is even more. K-Meleon is not freeing occupied memory and after some time it looks like it's trying to challening ff2 in "Who will eat more memory" contest.

Now one tab and it does occupy 75MB, minimize, restore and it will be only 14MB. Having more tabs (layouts actually in K-Meleon terminology) the trick is loosing its grip and smooth the most crucial difference between K-Meleon and firefox. (But why is needed at all?)

Any idea how to make it less resource hungry again?

I'm using K-Meleon 1.1.6. Now one tab and it does occupy 23MB, minimize, restore and it will be only 6MB. Quite a difference between mine and yours!

I don't know why is K-Meleon behaving different. Your stats responds to how it was acting previously in 1.1.3 version for me. Which is no any longer.

And I don't think that using AdBlock, Flashblock and ProfileBackup extensions can lead to such enormous effect. - Although I noticed it's having notoric troubles with acrobat reader (5) - ie when I will open a group with at least one acrobat reader window chances are high that K-Meleon gui will crash. It will stay in the memory but no graphical window. Also it's having trouble with killing acrobat reader after it's not needed, which seems to be the same for all mozilla based browsers.

zelgon: did you try to use Foxit Reader?
Mine is 1.1.5, my PC is a veteran and it always worked well (now with 2 tabs - 32MB). Yesterday & today it was pretty slow ( 1 tab - 75MB ) but after I ran AVG it's workin' well again. (I'm not a geek so I don't know if that was really the problem - AVG caught some tracking cookies)
!

I never tested this version before but... do I have to modify each macro I have, not because they have errors, that indeed, they haven't (only, maybe one or two lost semicoloms), just because I have loads of macros and the new parser doesn't pass anything? Not only that, after this, appears a window error from a variable not initialized....... what is supposed to mean that? Then the browser crash.

This broke me, really...

I had a lot of work to port my config from the 0.x version to 1.x, but now, this 1.5 killed me. Literally, killed me.

EDIT:

For example... what is wrong here? I just followed the macro language statements: