429701 - It's possible to make the browser un-use-able by calling certain javascript functions from flash.external API

Status: RESOLVED INCOMPLETE

(External Software Affecting Firefox Graveyard :: Flash (Adobe), defect)

Description

[Geert-Johan Riemer]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; nl; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; nl; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14

When calling large, cpu-using, javascript functions, such as huge AJAX content handling and layout-functions,  fromout flash (using the external API) the browser freezes. If you're unlucky, the whole OS freezes, and A hard-reset is the only solution..

Owh and uhm, you probably have heard this a lot already but, why is it still posible to execute this javascript?:
while(1) { alert("you're screwed, close your browser using ctrl+alt+del"); }

Reproducible: Couldn't Reproduce

Steps to Reproduce:
1.
2.
3.



  PC specs:
Mobo: Asus P5N32-E SLI+ (680i chipset)
CPU: Intel Q6600 Quad-Core (still normal clocked)
RAM: 2GB
GPU: Asus 8800GTX 756MB
HD: 4x500Gig WD 7,200 S-ATA/300 in RAID10 config (1200MB/s read, 600MB/s write)

  OS:
Windows XP SP2 (dutch)

  Internet speed:
max 550 KB/s down
mac 250 KB/s up
(bad copper and 8 KiloMeter to DSLprovider-station :s)

Anything else? mail me squarc^AT^gmail^dot^com

Comment 1

[Martijn Wargers (dead)]

Do you have an example page somewhere with that specific flash?

> Owh and uhm, you probably have heard this a lot already but, why is it still
> posible to execute this javascript?:
> while(1) { alert("you're screwed, close your browser using ctrl+alt+del"); }

That's bug 61098.

Comment 2

[Geert-Johan Riemer]

not anymore I'n sorry,
Its realy easy to do so though, just start a flash, totaly empty with in frame 1 this actionscript:

while(1) {
import flash.external.*
ExternalInterface.call("jsFunction", n["extra parameters"]);
}

and in the html:
<script type="text/javascript">
 function jsFunction() {
  //large stuff that uses some CPU..
 }
</script>

that'll do it..

Comment 3

[Geert-Johan Riemer]

owh, and by now I think I had to fill that in at the reproduce part :p (srry, I'm from Holland and I though reproducible meant something else)

Comment 4

[timeless]

So, I'm not sure this is actually a flash bug, it might rightfully belong to Browser, please feel free to bounce this back.

Comment 5

[Benjamin Smedberg]

I'm closing a lot of bugs which are filed as Adobe Flash bugs which are either irrelevant, not actionable, or not serious enough to track in the Mozilla bug tracker. For the most part, Flash bugs should be filed in Adobe bugbase, and we'll only track a few highly-critical issues in the Mozilla tracker.

Comment 6

[BMO Automation]

Version and milestone values are being reset to defaults as part of product refactoring.