115613 - When I try to select the RPG at the menu, browser stops responding and eats all RAM

Status: VERIFIED DUPLICATE of bug 112241

(Core :: Layout: Form Controls, defect)

Description

[Mika Yrjölä]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.6+) Gecko/20011212
BuildID:    2001121221

When I go to the URL mentioned in the bug description and try to choose the RPG
I want to read amusing stories about, instead of transfering me to the page I
want, Mozilla just stops responding and seems to eat memory until it (or in case
of kernel 2.4.15pre7 the whole machine) dies or Mozilla is killed.

Reproducible: Always
Steps to Reproduce:
1. Go to the URL mentioned in bug description.
2. Choose a RPG at the menu at the top of the page
3. See what happens.

Actual Results:  The browser stops responding and eats eventually all RAM it can
get.

Expected Results:  The browser should transport to the page that has been
selected from the menu.

Reportedly, the same effect happens with Galeon, although I haven't tried it myself.

My machine is RH7.0 + updates.

Comment 1

[Karl Johan Kleist]

Build ID: 2001 12 15 08. Windows 2000.

Wow - what a memory sucker! I've never seen something like this.

When I selected "Star Trek RPG" from the pick list, my > 1 GB swap partition
almost filled up in less than 30 seconds.

Suggest OS => all

Comment 2

[Karl Johan Kleist]

This problem may be JavaScript related, since the pick-list "Dice Tales" at the top
isn't even rendered if JavaScript is disabled.

Comment 3

[Dimitrios]

Please correct if the following are wrong. I think the problem is inside
function  selectaplace(form) which is called once a selection is made. In this
function, the following condition (line 51):
if (appname == "Netscape" && appversion >= 3)
leads to a block containing this line:
form.select1.options[formindex].text=x;
That line causes infinite iterations of selectaplace(form). It seems that
assigning a new a value to an element of the options list produces an onchange
event in the form, therefore producing infinite looping.
Probably a dupe of bug 112241.

*** This bug has been marked as a duplicate of 112241 ***

Comment 4

[Dimitrios]

I tested the aforementioned site a few days ago and it was still hanging. Works
without problems now (build 2002012903). Verifying duplicate.