Closed Bug 175939 Opened 22 years ago Closed 22 years ago

Pages load with grey regions at random times

Categories

(Core :: Layout, defect)

Product:
Core
Component:
Layout
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED DUPLICATE of bug 181293

People

(Reporter: u4664, Unassigned)

References

Details

Attachments

(1 file)

PNG of Mozilla with Gray Navigation Bar
64.82 KB, image/png
Details
Sometimes when I load a page, either by clicking a link, using a bookmark or whatever, the new page will load over the current one. But the old page still remains, none of the text from the new page appears, and regions for the new page's images are displayed as grey boxes. If this page load was done on a tab in the background, switching over to this tab will produce just a blank grey page, no text, no images, nothing. A simple reload will produce the new page correctly in either of the above cases. This problem seems to occur randomly, I haven't been able to discern any pattern. This never happened pre-1.2b. I'm running build 2002101612 on OS X 10.2.1.
I've been seeing this on occasion as well, haven't filed anything yet as I have yet to see a pattern either. It seems to happen only once out of many page loads.
Confirmed using FizzillaCFM/2002101808 on 10.1.5. This has been happening throughout the application; in browser windows, in MailNews, in dialogs, etc., with no discernable pattern.
Status: UNCONFIRMED → NEW
Ever confirmed: true
I'm seeing simlar behavior with 2002102303 on 10.2.1, but with a slight variation: On some page loads the entire page loads grey. Unfortunately, I just switched to OS/X, so I have no idea when this started happening...
I've since found that this problem can occur with dialog boxes too. Again, no discernable patterns, except maybe heavy disk activity.
I have seen this in Mail/News. It definatly wasn't pressent in the 1.1 release but I've seen it with just about every release of 1.2 upto and including build 200201612. I click on an email in the list and all I get is a dark grey rectangle where the mail should be. clicking on the email again will often, but not allways, display the email correctly. This behaviour feels like Mozilla not having enough memory to render the contents of a window and thus giving up early. However, I'm sure there is plenty of free memory on my system.
I also have not seen this bug in 1.1 (or 1.2a I think), but am seeing it now in 1.2b. I am using Mac OS 10.2.1 build 20021016.
*** Bug 178633 has been marked as a duplicate of this bug. ***
I've also seen it in various windows (browser, mail) running on the latest MacOS X. In the browser the page seems to be loading but instead of displaying it the greyness spreads over the page by rectangular sections. This behaviour started with 1.2b.
I've been seeing this a LOT lately, and I don't think it's directly related to a memory shortage. I have hundreds of megs of RAM available (not to mention gigs of room for swap) and the Mozilla process isn't *that* big yet. In any case, this is one of the more annoying bugs I've run across recently. For me, I never get pages loading with grey regions. It's just that the entire page fails to redraw when a new page is loaded, and I see the grey if I switch away and back to the tab or try to scroll. Has there been any progress in tracking this down? What can I do to help resolve this?
Why isn't this one of the 1.2 blocker bugs? This makes Mozilla one of the worst browsers around. Sometimes clicking a link retrieves the page but the browser window doesn't change in the slightest - no gray boxes - but all the links appear "dead". It's like the browser has frozen, except that all the menus still work and clicking reload will properly display the page. I'm sure lots of people are not clicking reload and and instead think the browser just sucks. I've also seen this affect only an iframe within a page, for instance like on the tinderbox page. Click the link for "Tree Status" from the mozilla main page will load tinderbox just fine, but the iframe will be gray.
I currently use Mozilla build 2002111603 and 10.2.2, and this bug seem to occur randomly. I appeared in 1.2b (was ok in 1.1a) and never disapeared; I was frustrated and tested 5 nightly build in the 1.2b "branch". this bug was present on all build, and on all system vers. (10.2, 10.2.1 and 10.2.2)
Moving the bug out of Browser General into Layout for further triaging. Greg, you should remember the next time to put a bug into an appropriate component (even if you're not sure whether it's the correct one) before confirming. Else only our overburdened Asa will sometime in the far future have a look at it. And it would be very helpful, if everyone who's seeing this bug, could try hard to come up with reliably reproducable steps to trigger this behaviour. This would make fixing it a lot easier.
Assignee: asa → other
Component: Browser-General → Layout
QA Contact: asa → ian
Note that this could be associated with bug 181293.
I have been trying to reproduce it with no luck. I can tell you how it is different from bug 181293 - I am not using anything with "tree widgets" when it happens (in fact I have not been able to reproduce that bug at all). Yesterday it occured shortly after starting Mozilla up and just doing some simple web browsing. I thought it might have been related to using the "Back" button, but that does not pan out so far. I have seen it on two computers, one running MOSX 10.2.2 and one running 10.1.5. And when you do a "view source" on the gray or unchanged page, you do see the html for the correct page.
I see this quite frequently while reading news. I click on a message and the body area isn't displayed, instead I get the dreaded grey rectangle. I can repeatedly click on other messages and back to this one and each time the same message is displayed as a grey rectangle. In fact the only way to read these messages is to click reply and read then in that window. Simply opening a new window with the message isn't sufficient to make the page render. I haven't noticed anything special about the particular messages that may cause the problem. I'll look further at the message headers to see if I can spot a pattern when it next happens. Another place I've seen it is occasionally when a dialog box slides down from the title bar. For example the 'advance to next message in xxx folder' message. Hitting escape and repeating the next button will make the dialog display correctly.
*** Bug 181987 has been marked as a duplicate of this bug. ***
This isn't constrained to content portion of window. I've opened up a new window and had the navigation bar be gray (similar to Bug 181293, but without the tree widget step). Doesn't depend on site; is random. I didn't see this in the 1.2 Alpha builds. (MacOS X 10.2.2, Mozilla 20021126)
PNG of Mozilla with Gray Navigation Bar This is build 2002112607 MachO on MacOS X 10.2.2. Hiding and showing the Nav bar remains gray as does resizing the window. Unlike bug 181293, no tree widget in window from which this window was spawned.
I have had this bug too, and reload will fix it. However, if it happens when a small window comes sliding down from the top (under Max OSX) for a dialogue then THE ENTIRE MOZILLA IS TOTALLY LOCKED UP! The only thing to do is kill the entire beast and start over again. Just now this killed a session I was working with - lots of tabs open and in the middle of ordering something. It is a serious problem and so I propose that it be set to critical. The browser becomes useless with it happening. This seems to be related to Bug 176718, please confirm and merge.
Happens quite often but never had a crash or freeze related to it (and I surf a lot.. ;)
What Tom describes in comment 19 isn't really a crash or a hang. The problem is that a dialog appears, but is entirely grey (no text or controls are visible). The keyboard still works, though (try pressing return; the default button will activate).
Technically, you are right, but I didn't dare hit return because I didn't know what the default was and I couldn't get to the other options. The page FROZE all other mozilla windows and there was not way to back out of it. So it is, from a user viewpoint, a complete hang.
What Tom (comments 19 and 22) and Greg (comment 21) describe are related to my earlier comment (comment 4). This bug seems to affect anything that Mozilla renders, including its custom dialog boxes (e.g. cookie warnings, etc.). Looks like its related to Gecko or a similar module?
CCing a few people so this bug gets a bit of triaging love. Ian Hixie: How does triaging in this component normally work? Is it reasonable that there is no live default assignee for layout bugs?
Sounds like it could be a Mac Widget/GFX code problem.
*** Bug 176718 has been marked as a duplicate of this bug. ***
Duping to the more useful bug. *** This bug has been marked as a duplicate of 181293 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: