Typing:

Ctrl-L, then t

in the address bar terminates immediately all browser windows.

Really ANNOYING. Any site beginning with "t" requires "www." typed first.

How do I stop this ODDBALL termination?

Thanks

Which K-Meleon version ?
Which os ?

A+

---

Mozilla/5.0 (x11; U; Linux x86_64; fr-FR; rv:38.0) Gecko/20100101 Ubuntu/12.04 K-Meleon/76.0

---

Web: http://jujuland.pagesperso-orange.fr/
Mail : alain [dot] aupeix [at] wanadoo [dot] fr

---

Ubuntu 12.04 - Gramps 3.4.9 - Harbour 3.2.0 - Hwgui 2.20-3 - K-Meleon 76.0 rc

---

1.5.3 on Win 2K

Quote
Terminator
Typing:

Ctrl-L, then t

in the address bar terminates immediately all browser windows.

It is a known bug.
The count of t's in your history triggers the crash.

Browser Crashing When I Type 'A' Into URL Bar

You can reduce the size of your history in steps
to prevent browser termination.

Or, you can compile it yourself using the
information in the link above.

OMG! Thanks, DeadLock, for confirming this oddball bug!

Now, I want to make sure that I understand my options.

Option 1:
     a.) Do I have to do both of these?
              Tools>Privacy>Clear Data>Clear History
              Tools>Privacy>Clear Data>Clear URL Bar History
     b.) How often do I have to clear them?
     c.) Which values must I not exceed for these (Preferences>History):
              Keep a list of pages visited in the last X days.
              Keep a list of X most recently visited locations.

Option 2:
     You mentioned, in lieu of the above, compiling the code freshly.
     I don't know how to do that.  I presume that I am setting some
     history value differently (to solve the bug) and then compiling
     that changed source to a new EXE.  I didn't see steps for that 
     in the link you provided.

Thanks!

P.S. The above History values are currently set to 365 and 50, respectively.

Quote
deadlock

Quote
Terminator
Typing:

Ctrl-L, then t

in the address bar terminates immediately all browser windows.

It is a known bug.
The count of t's in your history triggers the crash.

Browser Crashing When I Type 'A' Into URL Bar

You can reduce the size of your history in steps
to prevent browser termination.

Or, you can compile it yourself using the
information in the link above.

1.) I did not find this bug in the bug tracker.
Under which description or bug number is it listed?

2.) IMHO reducing the size is the only viable opinion.


3.) To compile it You need a commercial version of VC. Preferably You'd use/need VC 8 so that the module uses the same runtime as the rest of K-Meleon 1.6.

AFAIK only Dorian has managed to set up his VC8 so that it generates stable K-Meleon.exes. Else I'd volunteer to compile the changed code/fix.



Edited 1 time(s). Last edit at 03/03/2012 03:03PM by guenter.

Thanks for replying, Guenter. This bug hits me so often, it has happened twice since my post!

Does anyone have more info on this bug and how to combat or fix it?

Thanks

Quote
Terminator


Does anyone have more info on this bug and how to combat or fix it?

deadlock has most info about this bug. So he is the most competent answerer.

I have seen reports before - crash with this or another letter. But I had not understood that all these reports were all about the same bug.

Fix AFAIK: Only the recompiled Exe will fix it for good.

Workaround AFAIK: Reduce the history that is kept.

AFAIK: browser.history_expire_days must be reduced to achieve reduction.
I use 9 days and never encountered the bug.

Clear history when You encounter it or reduce the days kept until You are free of the effects of the bug.



Edited 1 time(s). Last edit at 03/04/2012 04:06AM by guenter.

Quote
guenter
1.) I did not find this bug in the bug tracker.
Under which description or bug number is it listed?

No, there is no one open.

I was going to, but I didn't create it. Lazy me.

The bug consists in what Sirias told me in the past in my rants about switching to 1.6. I didn't know it happened to 1.5.

Anyway, the fix recommended is to clear History, what I will not.


But, to clear the bug, it happens when you type a character that has too much references in a cross check to the full history. Why does a full check with the history, is where it is the bug, because, for example, in 1.1.6, didn't happen and probably the checks were too against the full history.

So, with that behavior, when you type a character, or, better said, an string, that matches lots of entries, there is a memory overflow and crashes.

For example, in 1.6b2 happens to me a lot. I tend, as is normal to every internet user, to write www.whatever.com. When you type www., comes the memory overflow (loads of matches for www., what is normal, by the way) and crash. No time for crashreport plugin to catch the error.


EDIT: bug reported

I marked it as k-meleon bug because I don't know at what extent may be the history plugin the only responsible of the crash.



Edited 2 time(s). Last edit at 03/04/2012 05:23PM by JohnHell.

Thanks, Guenter and JohnHell, for responding most recently, and thanks to all who kindly took the time to comment on this bug.

I shall clear and reduce the history kept, per your advice, Guenter.

JohnHell, I am glad that you documented this issue via the bug report.

I hope that the wizards who program K-Meleon will fix this vexing bug, which manages to escape being reported in any crash report.

A few final thoughts...

Contrary to Microsoft's press releases that diminish it, there is a significant audience of Windows customers who do not use later versions of the product. Whether because of personal preference; lack of funds to buy everything all over again; limited older hardware; etc., these neglected customers may find refuge in helpful, community-supported software like K-Meleon that does not abandon them.

As a Windows 2000 user who has hardware drivers and diverse software that continues to be fully functional (and, often, still supported and updated), I have paid particular attention, over the years, to apps that still work great for Windows 2000. For some of them, a new version is subsequently released that breaks this compatibility, but not for any technically necessary reason: The break is due to nothing more than something akin to a default compiler setting imposed by Microsoft, put there to slip by developers silently and later frustrate customers and compel them to upgrade to XP (or later). For example, the build is now referencing some XP-only DLL that is totally irrelevant and unnecessary, and this dooms backward compatibility. The developer may not even realize this break, or, if he does, resign himself to labeling the newly compiled version with the requirement "XP or later" (perhaps, subconsciously buying in to Microsoft's PR fiction that "everyone is on XP, by now.")

I am grateful that K-Meleon continues to serve us Windows 2000 users.

Quote
Terminator
As a Windows 2000 user who has hardware drivers and diverse software that continues to be fully functional (and, often, still supported and updated), I have paid particular attention, over the years, to apps that still work great for Windows 2000. For some of them, a new version is subsequently released that breaks this compatibility, but not for any technically necessary reason: The break is due to nothing more than something akin to a default compiler setting imposed by Microsoft, put there to slip by developers silently and later frustrate customers and compel them to upgrade to XP (or later). For example, the build is now referencing some XP-only DLL that is totally irrelevant and unnecessary, and this dooms backward compatibility. The developer may not even realize this break, or, if he does, resign himself to labeling the newly compiled version with the requirement "XP or later" (perhaps, subconsciously buying in to Microsoft's PR fiction that "everyone is on XP, by now.")

I am grateful that K-Meleon continues to serve us Windows 2000 users.

Take note:

Win2kGaming or Windows 2000 Gaming Forum

Fixes for games and applications to run XP applications under Windows 2000 by tricking dlls calls via system dll wrappers. Some kind of Windows 98 KernelEx but for Windows 2000.

Quote
JohnHell
So, with that behavior, when you type a character, or, better said, an string, that matches lots of entries, there is a memory overflow and crashes.

For example, in 1.6b2 happens to me a lot. I tend, as is normal to every internet user, to write www.whatever.com. When you type www., comes the memory overflow (loads of matches for www., what is normal, by the way) and crash. No time for crashreport plugin to catch the error.
EDIT: bug reported

I marked it as k-meleon bug because I don't know at what extent may be the history plugin the only responsible of the crash.

It is already in CVS.
This bug was fixed last year in urlbar.cpp Revision 1.18.

Quote
deadlock

It is already in CVS.
This bug was fixed last year in urlbar.cpp Revision 1.18.

Did I search under the wrong keyword?


Or Does this mean that the bug tracker is outdated?



Edited 1 time(s). Last edit at 03/18/2012 10:35AM by guenter.

I think that means was known (there was no need for a bug report), was fixed, but was not released :/

And then we came here to report a bug already fixed, but only in the CVS :/