Summary: Screen becomes white after viewing and downloading many images
Creator:pasfr Date:2003-01-13 22:38:04
Project:K-Meleon Owner:.Nobody
Status:Closed Severity:Normal
Version:Unknow Target Version:Unknow

I am using K-meleon for 1 day,K-meleon is simply fantastic
There is 1 big bug ,namely after vieuwing and downloading images for a while , the screen becomes white ,when you save the image and reboot , the view of the stored image is normal, this is the same bug IE3 (windows 95) got ,this has been repaired since IE4
This is really a nice browser,so d' ont touch the layout , it is clean and perfect
Improvements I suggest :
Resume downloads of images of files , there should be a swith that this could be
done automaticly after some time , this should improve on Opera
On rightcick mouse a save option,that saves the image or file in the current directory
without asking and popups

Pas Francois
pasfr@hotmail.com

Comments
amutch  2003-01-29 22:53:25
What version of K-Meleon are you using? What OS are you running it on?
amutch  2003-01-29 22:54:21
[Changed Summary from "" to "Screen becomes white after viewing and downloading many images"]
Kidman  2003-07-24 02:38:04
It's not a problem of viewing images. After a while K-Meleon starts behaving strange and doesn't refresh the content of the window properly. If you try to mark the page with the mouse, you maybe abale to get at least the marked text and images visible, but not the whole page.
To get it working again, you have to kill your k-meleon.exe instance and start it again (when using the loader, what I do).
I don't know under what circumstances it does happen, but it appears to happen when you got your k-meleon.exe a long time in the memory (when using the loader). It's surely one of the most annoying bugs.
Kidman  2003-07-26 01:31:18
well...this just happened under Windows 98SE to me. Never under Windows 2000.
asmpgmr  2003-10-18 10:42:16
I've seen this with 0.7 (Mozilla 1.2) and 0.7.5 beta (Mozilla 1.4.1) after viewing a LOT of images. It's due to a GDI memory resource problem in Mozilla that there's supposed to be a fix for now. Note the problem only affects win9x, win2000 has better memory management. This bug should be changed to Open - Mozilla bug.
asmpgmr  2003-10-18 10:42:55
I've seen this with 0.7 (Mozilla 1.2) and 0.7.5 beta (Mozilla 1.4.1) after viewing a LOT of images. It's due to a GDI memory resource problem in Mozilla that there's supposed to be a fix for now. Note the problem only affects win9x, win2000 has better memory management. This bug should be changed to Open - Mozilla bug.
rmn  2003-10-19 18:09:35
Moving bug 450 here.

From #450:
If you look in task manager, k-meleon's memory usage increases after every picture, and for me, it usually stops working once it gets to 32 megs (i have a 16 meg memory cache if that matters).

Is this really a Mozilla bug? And if there's supposed to be a fix, is it working?
[Changed Status from "Unconfirmed" to "Open"]
jsnj  2003-10-25 23:43:45
This is still happening in 0.8 beta build 833
Mark I.  2003-11-21 16:42:12
Still present in 0.8.0, build 844, on Win95. (Seen on a system w/ 128MB RAM)
leggewie  2003-12-15 08:24:35
Still present in 0.8.1 Win98. I'd say the problem is occuring more frequently now than in version 0.7.
amutch  2003-12-16 19:55:58
I believe this is the appropriate Mozilla bug:

http://bugzilla.mozilla.org/show_bug.cgi?id=205893

Please try the test cases to confirm.
Ulf  2003-12-17 01:15:41
There is also mozilla bug 204374: http://bugzilla.mozilla.org/show_bug.cgi?id=204374
and mozilla bug 184933: http://bugzilla.mozilla.org/show_bug.cgi?id=184933
jsnj  2003-12-22 01:32:35
The behavior described by Kidman still happens in 0.8.2b. Just happened to me 2 consecutive sessions. I wasn't viewing images in either session. Win98.
Kidman  2003-12-22 07:42:58
That behavior got worse since 0.8. It doesn't help that much anymore to kill the k-meleon.exe or restart it. It may work for a short while again and that behavior happens even sooner after a restart of it. You have to reboot your computer to get it working properly again.
leggewie  2004-02-28 09:18:29
Is this bug being worked on? I think it should be #1 priority!
leggewie  2004-04-18 03:51:55
Please see discussion about the bookmarks plugin in bug 681 as I assume the phenomena described there might be related to this bug.
leggewie  2004-04-18 06:46:20
a patch has been recently checked in for tracker mozilla bug 205893 (see comment 84).
rmn  2004-11-04 03:08:50
Reminder: we need to remove the text refering to this in the Release Notes if it is indeed fixed.

Should we test first or just mark as Fixed?
[Changed Status from "Open" to "Open - Mozilla Bug"]
ra  2004-11-06 17:31:07
This might also be related with bug 715, leaking bookmarks toolbar = bug 681 (I hope both get fixed with .9, the beta looks good right now) and perhaps some layer or other problems. In any case we need a common *testcase*! :-) BTW: Win 9x users will probably note that problem more easily.

Bugs should never be marked as fixed without any prior testing.
amutch  2004-11-26 21:20:23
This has been tested pretty thoroughly and reported fixed in beta 3. Also added to the Release Notes for 0.9.
[Changed Status from "Open - Mozilla Bug" to "Fixed"]
ra  2004-11-27 06:03:30
Yep, this is fixed, and it has probably been held responsible for some time now for crashes that were in fact caused by bug 715, see e.g. Eyes-Only's testing here: http://kmeleon.sourceforge.net/forum/read.php?f=1&i=19611&t=19611
leggewie  2005-02-20 10:47:33
I am sorry to say, I witnessed this bug again today with Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.4) Gecko/20041010 K-Meleon/0.9b. Actually I am writing this report with the browser exhibiting that behaviour. What is more strange is that it occured while the computer wasn't under heavy load. I had about 7 or 8 layers open and resources were 34% system, 34% user and 61% GDI. Not a whole lot of other programs were running at the time this occured.
jsnj  2005-02-20 19:50:29
Well, you're using a beta and one based on a different Mozilla backend. K-Meleon v0.9 final has been available for over a month. If you see the behavior in the final, then report it. Otherwise, it's irrelevant.
rmn  2006-01-14 21:52:22

[Changed Status from "Fixed" to "Closed"]

SourceForge Logo