Closed Bug 181987 Opened 23 years ago Closed 23 years ago

Sometimes pages aren't displayed, though load is indicated as finished

Categories

(Core Graveyard :: GFX, defect, P3)

Product:
Core Graveyard
Component:
GFX
Platform:
PowerPC
macOS
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 181293
Milestone:
mozilla1.4beta

People

(Reporter: bugzilla, Assigned: sfraser_bugs)

References

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 5.22; Mac_PowerPC) Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.3a) Gecko/20021118 Sometimes a page does not get rendered if hiting a link. Happens on different sites with no special content. Mozilla thinks it shows the new page but does still show the last page - you can see it because mozilla does no longer recognize the links on the old page (no change of cursor etc.). Scrolling leads to grey areas on top or buttom (depends where the old page was). Reloading the page did work in all cases. The bug is not reproducable, happens once or twice a day since some weeks (I download the nighty build randomly so I can't say when it started, I guess one or two month ago but seems to get worser) Reproducible: Sometimes Steps to Reproduce: hostinfo Mach kernel version: Darwin Kernel Version 6.2: Tue Nov 5 22:00:03 PST 2002; root:xnu/xnu-344.12.2.obj~1/RELEASE_PPC 1 processor is physically available. Processor type: ppc7400 (PowerPC 7400) Primary memory available: 1024.00 megabytes. 2x ATI Rage128, no speacial extensions loaded, "just a normal 10.2.2"
Yes, I've seen this too. I've wondered if it isn't the same problem as or related to bug 175939.
Assignee: asa → kmcclusk
Status: UNCONFIRMED → NEW
Component: Browser-General → GFX Compositor
Ever confirmed: true
QA Contact: asa → ian
Summary: Page get not rendered randomly when clicking a link - page does not change - reload works → Sometimes pages aren't displayed, though load is indicated as finished
*** Bug 182038 has been marked as a duplicate of this bug. ***
175939 seems to be simular/same though I never got a blank grey page. It's just like you think you did not hit the link but then mention that all (still visible) links are dead (in fact, mozilla believes to show the new page so there have to be no links..). Scrolling does always show grey top or bottom areas. Btw.., today I found another "grey effect" while searching a webpage for a word. The first word was not on the page so an error message popped up ("the text you entered was not found"). I searched for a second word which was neither on the page. The not-found-message was then only a grey box and I had to guess where the OK-button is.. ;) A more cosmetic thing: The OK-button to dismiss the "normal" not-found-message get two white lines in the blue area when clicked. *** This bug has been marked as a duplicate of 175939 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Hmm, I think it's a bit premature to dup this just yet. Let's wait for some actual evidence.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
This happens to me repeatedly throughout every day of use. It did *not* happen under 1.1. I click a link, it seems to load, the status bar changes, etc. The old page is dead (no links can be clicked) but there is no new page. Hitting reload takes me to the new page. Hitting back takes me to the old page. I can get control of my browser back by either of these methods. This is very annoying!
See also bug 181293, bug 184972 I run into this frequently on OS X CFM 2002121908, and have for a couple months.
This is different behavior. It should be under a different bug report. Here, the new page seems to load, but is not displayed. The visual indicator is the progress bar. Instead of displaying the new page, the old page is left on display. The old page is sort of a ghost, as none of the links/buttons/et c. respond to mouseevents, et c.
They're definitely different symptoms, but my gut feeling (as someone who has done Cocoa programming on OS X) is that they're at least related. The end result of both is that the new page is not being displayed. My gut feeling is that the only difference is one of them is invalidating the visible rect (thus causing it to clear what was there, but draw nothing because the draw routines haven't been hooked in correctly), and the other is not invalidating the visible rect (so it neither draws it nor clears it). Whether the rect got invalidated or not could be a symptom of the actions that led up to it or what other windows were present at the same time. Unfortunately I've never even touched the source code of Mozilla before :) so I have no idea how Mozilla is actually doing it.
-> Simon
Assignee: kmcclusk → sfraser
Status: REOPENED → NEW
Priority: -- → P3
Target Milestone: --- → Future
Need better steps to repro. After it goes bad, does a subsequent page load (e.g. from a bookmark) display correctly? What if you close the window, and open a new one?
Status: NEW → ASSIGNED
Target Milestone: Future → mozilla1.4beta
Aside from the undrawn page, the browser seems to function completely normally, including loading pages from bookmarks, opening new windows, etc. Clicking "Refresh" solves the problem in 100% of the cases I've seen, but this is of course undesirable in cases where the undrawn page was the result of a POST.
I still get this on 2003011203 MacOSX-trunk. I have no clue how to reproduce it. about 90% of the time, the previous page just stays there, but nothing is clickable anymore. The other 10% of the time I get that blank gray window. This is very intermittent, and just clicking reload fixes it every time when it does happen. Except it's not very fun (as mentioned in the previous comment) when the page that fails to load is the result of a POST. :)
Seeing how the discussion has turned in bug 181293, I feel even stronger now than I did before that both of these bugs are just different symptoms of the same issue. I think this should be marked as a duplicate of bug 181293 (or at least depends on it). If it's marked a dupe, the summary on that bug should probably be broadened a bit to indicate the full scope of the discussion on the bug.
*** Bug 192637 has been marked as a duplicate of this bug. ***
*** Bug 185724 has been marked as a duplicate of this bug. ***
*** Bug 195590 has been marked as a duplicate of this bug. ***
Bug 181293 was marked FIXED, and I'm betting that checkin fixed this bug, too. Downloading today's build to find out, and will report back.
Well, I've been using yesterday morning's build for almost two days now on two different OS X laptops and have not run into this once yet on either. Usually I was running into it at least a couple times a day. Anyone else?
Sounds good to me. *** This bug has been marked as a duplicate of 181293 ***
Status: ASSIGNED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → DUPLICATE
I used yeseterday's 1.4a nightly (March 12) for about 3 to 4 hours of web surfing without the appearance of this bug. I would recommend marking this bug as resolved and reopen if the bug reappears.
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.