Closed
Bug 298565
Opened 20 years ago
Closed 20 years ago
FF is crashed with 2 JS strings
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: gentuu, Unassigned)
Details
Attachments
(1 file)
|
168 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050522 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050522 Firefox/1.0.4
This kills FF (even in 1.0.5 beta!):
<html><body>
<iframe id="pocframe" name="pocframe" src="about:blank"></iframe>
<script type="text/javascript">window.frames.pocframe.print();</script>
</body></html>
Reproducible: Always
Steps to Reproduce:
1.Save the 4 strings into .html file
2.load it with any FF version
Actual Results:
> /opt/firefox/firefox
*** loading the extensions datasource
*** ExtensionManager:_updateManifests: no access privileges to application
directory, skipping.
*** loading the extensions datasource
*** ExtensionManager:_updateManifests: no access privileges to application
directory, skipping.
SessionSaver observer object: QI unknown interface:
{9188bc85-f92e-11d2-81ef-0060083a0bcf}
SessionSaver observer object: QI unknown interface:
{9188bc85-f92e-11d2-81ef-0060083a0bcf}
SessionSaver observer object: QI unknown interface:
{9188bc85-f92e-11d2-81ef-0060083a0bcf}
SessionSaver observer object: QI unknown interface:
{9188bc85-f92e-11d2-81ef-0060083a0bcf}
SessionSaver observer object: QI unknown interface:
{9188bc85-f92e-11d2-81ef-0060083a0bcf}
SessionSaver observer object: QI unknown interface:
{9188bc85-f92e-11d2-81ef-0060083a0bcf}
SessionSaver observer object: QI unknown interface:
{9188bc85-f92e-11d2-81ef-0060083a0bcf}
/opt/firefox/run-mozilla.sh: line 159: 31861 Segmentation fault "$prog"
${1+"$@"}
Expected Results:
Show an empty iframe or nothing, BUT NOT CRASH.
(?)
Crashes under Linux (different kernels) and WindowsXP (possible other wins).
Also this JS code crashes mozilla-1.7.8 (tested on Gentoo Linux/2.6.12)
Terrible thing...
|
||
Comment 2•20 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050622
Firefox/1.0+ ID:2005062207
WFM - No Crash
So, was this fixed already?
Or you just show "not crashing" on windows?
|
|
||
Comment 4•20 years ago
|
||
You can download the current trunk build from here
<http://www.mozilla.org/releases/nightly.html> and see if it has been fixed.
Does the attached test case trigger the crash? And can you please provide a
Talkback ID for the crash.
Yes, it works now w/o crash.
Great thanks!
Could this be ported to 1.0.5 from 1.0+ not to release a security fix version
with this great hole?
Thanks
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
|
||
Updated•20 years ago
|
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
|
|
||
Comment 6•20 years ago
|
||
Only bugs with patches get marked as fixed. -> WFM
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → WORKSFORME
Kevin,
so, can I hope this hole will be closed in 1.0.5 SECURITY (!!!!) fix release??
or I don't understand what is security release??
Thanks
Status: RESOLVED → VERIFIED
Sorry, but I can't leave this in WFM because it DOESN'T works on 1.0.X FF.
Status: VERIFIED → UNCONFIRMED
Resolution: WORKSFORME → ---
|
|
||
Comment 10•20 years ago
|
||
Bugs fixed on the trunk get marked as such. -> WFM
Nominating blocking 1.0.5 for Tux
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 20 years ago
Flags: blocking-aviary1.0.5?
Resolution: --- → WORKSFORME
|
|
Reporter | |
Comment 11•20 years ago
|
||
> Bugs fixed on the trunk get marked as such. -> WFM
>
> Nominating blocking 1.0.5 for Tux
So, as I see this still is not fixed in aviary1.0.5.
How can I help to add the patch from trunk in aviary?
|
||
Comment 12•20 years ago
|
||
first you'd have to find it. get a stack trace/talkback id (e.g. from 1.0.4).
personally i think this is beating a dead horse.
Version: unspecified → 1.0 Branch
|
||
Updated•20 years ago
|
Flags: blocking-aviary1.0.5?
You need to log in
before you can comment on or make changes to this bug.
Description
•