Closed
Bug 485332
Opened 16 years ago
Closed 16 years ago
javascript: print() function on page load crashes firefox with a segmentation fault
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: gregory.sacre, Unassigned)
Details
Attachments
(3 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.6) Gecko/2009011913 Firefox/3.0.6
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.7) Gecko/2009030817 Gentoo Firefox/3.0.7
I am developing a web application.
When clicking on a link, I force a new popup window and a print of this new page.
The javascript used for this page is in the end of the body part of the HTML page and is presented like this:
<script type="text/javascript">
onload = print();
</script>
When the page loads, Firefox crashes with a segmentation fault.
This also happens when Firefox is launched with the "-safe-mode" flag.
This was not happening with Firefox 3.0.6 (and previous).
Reproducible: Always
Steps to Reproduce:
1. Opens the web page containing the javascript "print()"
2.
3.
Actual Results:
Firefox crashes with a segmentation fault.
Expected Results:
Show the print dialog of the page
Reporter | ||
Comment 1•16 years ago
|
||
This is an "strace" log that reproduces exactly the problem.
Reporter | ||
Comment 2•16 years ago
|
||
Reporter | ||
Comment 3•16 years ago
|
||
These are by default in the Gentoo Linux building method for Firefox-3.0.7
Reporter | ||
Updated•16 years ago
|
Version: unspecified → 3.0 Branch
Comment 4•16 years ago
|
||
we need a GDB Stack trace with debug symbols and not a system Trace or a crash OD from our Crash reporter which is only available in a Mozilla.org binary build
Reporter | ||
Comment 5•16 years ago
|
||
I installed the bin version and I could not reproduce it.
I re-installed the source version and cannot reproduce since then.
I have no idea how or why but I propose to mark this bug as "NOT REPRODUCIBLE".
Thanks for your help!
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•