javascript setInterval works differently (wrong I assume) on linux 64-bit (possibly 32 bit as well)

RESOLVED DUPLICATE of bug 344439

Status

()

Core
DOM: Core & HTML
--
major
RESOLVED DUPLICATE of bug 344439
12 years ago
12 years ago

People

(Reporter: David oldford, Unassigned)

Tracking

1.8 Branch
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

12 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.0.5) Gecko/20060731 Ubuntu/dapper-security Firefox/1.5.0.5
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.0.5) Gecko/20060731 Ubuntu/dapper-security Firefox/1.5.0.5

when the javascript setInterval function is used with a small repeat time on windows (I have tested this) and firefox is unable to meet the demands placed upon it the interval is merely extended. On linux 64-bit javascript simply ceases to function. I'm running an AMD X2 3800 with 1GB of RAM if I go to the given link in Windows everything runs fine, if I go there in linux it runs for a couple of seconds and then freezes. I've tried playing with the javascript on the page and if I change the setInterval to a setTimeout with a 1 msec delay and then add a setTimeout with a 1 msec delay to the end of the rendering function things work fine, they also work fine if the delay on the interval is increased. I have not been able to test this on 32-bit linux yet.

Reproducible: Always

Steps to Reproduce:
1. create a webpage with javascript that calls setInterval to do a reasonably sized operation (like updating graphics)
2. systematically lower the timeout given to setInterval
3. all javascript on the page will freeze.

Actual Results:  
all javascript on the page will freeze

Expected Results:  
the setInterval interval should have been extended... I think I couldn't figure out what the Specs for Javascript intend to happen if setInterval can't do it's job correctly but I know that firefox on windows extends the interval

konqueror extends the interval automatically as does IE. I labeled this major because if AJAX apps start getting more involved and including animations or something of that nature older computers might **** out trying to use them instead of just slowing down. I was torn between major and normal however.

Updated

12 years ago
Assignee: nobody → general
Component: OS Integration → DOM: Level 0
Product: Firefox → Core
QA Contact: os.integration → ian
Version: unspecified → 1.8 Branch

Comment 1

12 years ago
Is this a dup of Bug 344439?
(Reporter)

Comment 2

12 years ago
It would appear so... I checked under Firefox and neglected to check under CORE. sorry about that.

*** This bug has been marked as a duplicate of 344439 ***
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.