Closed Bug 298013 Opened 20 years ago Closed 19 years ago

Lockups When Navigating Back And Forward on thin client

Categories

(Firefox :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: drichard, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050609 Firefox/1.0+
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050609 Firefox/1.0+

We have using Firefox for a long time now, and I am testing the Deer Park Alpha
1 release and I'm noticing that in some sites the [Back] button locks up.  It
seems to happen on sites with heavy shockwave content.  It doesn't happen every
time, or I would point you to that site. 

I did an strace on the running process and got the output below over and over
again, I'm hopeful that it's useful:

select(0, NULL, NULL, NULL, {0, 11000}) = 0 (Timeout)
gettimeofday({1119014302, 937377}, NULL) = 0
ioctl(44, SNDCTL_DSP_GETOPTR, 0xbfffd28c) = 0
ioctl(44, SNDCTL_DSP_GETOSPACE, 0xbfffd28c) = 0
select(0, NULL, NULL, NULL, {0, 11000}) = 0 (Timeout)
gettimeofday({1119014302, 948382}, NULL) = 0
ioctl(44, SNDCTL_DSP_GETOPTR, 0xbfffd28c) = 0
ioctl(44, SNDCTL_DSP_GETOSPACE, 0xbfffd28c) = 0
select(0, NULL, NULL, NULL, {0, 11000}) = 0 (Timeout)
gettimeofday({1119014302, 959375}, NULL) = 0
ioctl(44, SNDCTL_DSP_GETOPTR, 0xbfffd28c) = 0
ioctl(44, SNDCTL_DSP_GETOSPACE, 0xbfffd28c) = 0
select(0, NULL, NULL, NULL, {0, 11000}) = 0 (Timeout)
gettimeofday({1119014302, 970375}, NULL) = 0
ioctl(44, SNDCTL_DSP_GETOPTR, 0xbfffd28c) = 0
ioctl(44, SNDCTL_DSP_GETOSPACE, 0xbfffd28c) = 0
select(0, NULL, NULL, NULL, {0, 11000}) = 0 (Timeout)
gettimeofday({1119014302, 981370}, NULL) = 0
ioctl(44, SNDCTL_DSP_GETOPTR, 0xbfffd28c) = 0
ioctl(44, SNDCTL_DSP_GETOSPACE, 0xbfffd28c) = 0
select(0, NULL, NULL, NULL, {0, 11000}) = 0 (Timeout)
gettimeofday({1119014302, 992372}, NULL) = 0
ioctl(44, SNDCTL_DSP_GETOPTR, 0xbfffd28c) = 0
ioctl(44, SNDCTL_DSP_GETOSPACE, 0xbfffd28c) = 0
select(0, NULL, NULL, NULL, {0, 11000}) = 0 (Timeout)
gettimeofday({1119014303, 3367}, NULL)  = 0
ioctl(44, SNDCTL_DSP_GETOPTR, 0xbfffd28c) = 0
ioctl(44, SNDCTL_DSP_GETOSPACE, 0xbfffd28c) = 0
select(0, NULL, NULL, NULL, {0, 11000} <unfinished ...>
Process 31528 detached


Reproducible: Sometimes
Did you set the pref browser.sessionhistory.max_viewers to make fast
back/forward work ?
pref browser.sessionhistory.max_entries is set to 50, which is the default.  I
didn't change it.

I'm finding this happens when clicking on hyper links too, not just going back.
 Changing the title.

I'm trying to watch for a pattern.  It really seems to happen mostly on
shockwave heavy pages where items are animated and moving around.
Summary: Lockups Using Back Button → Lockups When Navigating Back And Forward on thin client
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.