what is your windows version and are you using a theme like xp luna or vista aero..if so, then you can confirm for us that there's a bug with the close button and windows themes.
please try this(if you are using a theme) open display properties >themes and select windows classic and see if you're still getting a crash(it might be a good idea to restart the computer after changing to classic theme before testing in kmeleon)
@disrupted
Windows XP SP3, but I don't use any theme like xp luna or vista aero. I'm a fan of simply interfaces
With Classical theme my Kmeleon crashes too! I don't know where the problem now...Strange situation.
it sounds like sp3.. both alex and james have sp3, maybe one more tester with sp3 can confirm the bug.. i think charlie caktus has sp3 too
alex, if you have the crash report plugin or download it and when it crashes it will prompt to send the dump to the project and maybe dorian can understand the bug.
i don't know anything about c++ or how dorian draws the button on the tab but there's this command backgroundstyle that has been reported to cause application crashes in other programs
Edited 1 time(s). Last edit at 09/25/2009 02:40AM by disrupted.
A family member has given me an old computer to test for him. I am pretty sure that it has only SP2 on it. If I can find time tomorrow, I will try the X on tab there and report results. I cannot find any mention of a 'luna' theme on my machine. The theme that is running just says 'modified'.
@desga2
When I change the pref manually (I read FAQ) Kmeleon has abnormal finished work in 1 second Crash again!
I can't open Kmeleon normally; the browser did not work absolutely until then while I have not removed manually a line
user_pref("browser.tabs.closeButtons", 1); from prefs.js
The interesting fact: I have removed a tabclosebtn.kmm from a folder of macroes and have again tried to change a configuration manually (in about:config). Also there was again an error in browser work! Thus, even without a tabclosebtn.kmm the browser breaks because of configuration change!
I changed theme to Classic and added the macro for the x toggle. When I tried the x toggle from the tab menu, KM failed. Bye the way, the Classic theme is ugly.
Going to try the other computer now. I have to connect it to display, KB and mouse first.
Update:
I tried the macro on the other machine. KM failed there also. The second machine has XP-Pro-SP2 (build 2600). My desktop has XP-Home-SP3 (build 2600).
In both cases, a little box appears in the lower right corner of the tab but I did not see an 'x' in the box. Shortly after the box appears the error message appears.
Does font have anything to do with x on tab? I have the following.
thanks james for the trouble.. atleast we know it's not themes and sp3 is innocent..it appears to affect some xpees and not all cause i have xp and it's working alright.. i think win 2k and 98 are not having problems, siria has win98 ..i wonder if some vistas might crash. it's definitely a bug but we can't tell what's causing it so dorain has to figure it out from a crash dump
Just copied my whole KM-folder over to a Vista32 notebook (Business/2006).
The close buttons work perfect, no crash.
(Just why over there the menus are displayed in double lines, meaning always an empty line in between?! That thing stays weird!)
I just sent crash report from my desktop unit, XP-SP3. Crash report was # 811.
Re: tab close button [x] toggle
Posted by:
mslayer
Date: September 26, 2009 05:28AM
The pref doesn't crash for me under win98se.
Could this problem be related to an special DLL dependency? or a graphics card configuration (color depth)? Screen resolution maybe? I'm shooting in the dark, but it can be anything 'cause these close-buttons don't look like the standard buttons.
Now I have received information that the discussed bug#1150detected in Windows7x86.
We must seriously examine the issue. Now, even on XP error and crash the browser is not at all computers. May be a conflict with some other setting (some else key in about:config)?
Colleagues, I have important information about the error. How do I tell one of the Russian colleagues, that the tab close button worked correctly without falling browser, you immediately when you first start to activate this setting. Then you can add any extension and the conflict will not. Just from the beginning to activate the option!
Alex is on to something. I had an unchanged install of 1.6 beta and following his information, I edited my prefs.js file and added the pref for x on tabs set to 1. KM opened just fine. I added tabs just fine.
Next I added one user macro. That worked.
Next I changed from bookmarks to favorites and changed the skin to Klassic. I also unchecked 'Display menu icons', 'Display website icons', and 'Display keyboard accelerater in menus'. KM failed on next restart.
I will have to go back and do the last changes one item at a time to see which thing caused the failure.
Update:
The problem item is 'Display website icons'. It must be checked for the x on tabs to work.
Edited 1 time(s). Last edit at 05/29/2010 06:23PM by JamesD.
it seems that when the icons are disabled causing the tab height to shrink and the close button doesn't find enough space to draw on the button triggering the crash
if that's the case, dorian should be able to fix it easily.. either with a fixed height for tab buttons or reducing the close button size to draw properly insiden the shrunken tab