Closed Bug 288048 Opened 20 years ago Closed 20 years ago

attempting to print this page causes firefox to crash 'memory cant be read'

Categories

(Firefox :: General, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 285701

People

(Reporter: mseedii, Assigned: bugzilla)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2 (ax)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2 (ax)

if you go to file/print or file/print preview firefox ends with message
memory cannot be read at 00x000000 
however if you click on the print this page control on the right hand side of 
the page, you get the page but you also get the follow message

[an error occurred while processing this directive]HTTP/1.1 200 OK Date: Mon, 28
Mar 2005 19:28:50 GMT Server: Apache PRAGMA: no-cache Cache-Control:
max-age=-3600 Expires: Mon, 28 Mar 2005 18:28:50 GMT Keep-Alive: timeout=15,
max=99 Connection: Keep-Alive, Keep-Alive Transfer-Encoding: chunked, chunked
Content-Type: text/html



Reproducible: Always

Steps to Reproduce:
1.go to the url 
2.select file /print or file/print preview
3.

Actual Results:  
firefox ends with memory cannont be read error

Expected Results:  
handle the error and continue
Confirmed
Should this be marked to:
Product: Core
Component: Printing
Severity: Critical

Can somebody get a talkback on this (due to personal reasons, I can't)?

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.6) Gecko/20050321
Firefox/1.0.2
I'm preparing a testcase for this one. Initial investigation looks like the
problem is a result of the stylesheet used.
Talkback ID: TB4666849x
Incident ID: 4666849
Stack Signature	0x00000000 58104bc1
Product ID	Firefox10
Build ID	2005032111
Trigger Time	2005-03-28 13:43:42.0
Platform	Win32
Operating System	Windows NT 5.1 build 2600
Module	
URL visited	https://bugzilla.mozilla.org/show_bug.cgi?id=288006
User Comments	Testing but 288048 (which should be confirmed and marked to critical)
Since Last Crash	8157 sec
Total Uptime	191085 sec
Trigger Reason	Access violation
Source File, Line No.	N/A
Stack Trace 	
0x00000000
nsIView::Destroy 
[c:/builds/tinderbox/Fx-Aviary1.0.1-l10n/WINNT_5.1_Clobber/mozilla/view/src/nsView.cpp,
line 251]
nsSubDocumentFrame::Destroy 
[c:/builds/tinderbox/Fx-Aviary1.0.1-l10n/WINNT_5.1_Clobber/mozilla/layout/html/document/src/nsFrameFrame.cpp,
line 568]
nsLineBox::DeleteLineList 
[c:/builds/tinderbox/Fx-Aviary1.0.1-l10n/WINNT_5.1_Clobber/mozilla/layout/html/base/src/nsLineBox.cpp,
line 302]
nsFrameList::DestroyFrames 
[c:/builds/tinderbox/Fx-Aviary1.0.1-l10n/WINNT_5.1_Clobber/mozilla/layout/base/src/nsFrameList.cpp,
line 129]
nsFrameList::DestroyFrames 
[c:/builds/tinderbox/Fx-Aviary1.0.1-l10n/WINNT_5.1_Clobber/mozilla/layout/base/src/nsFrameList.cpp,
line 129]
nsFrameList::DestroyFrames 
[c:/builds/tinderbox/Fx-Aviary1.0.1-l10n/WINNT_5.1_Clobber/mozilla/layout/base/src/nsFrameList.cpp,
line 129]
nsTableFrame::Destroy 
[c:/builds/tinderbox/Fx-Aviary1.0.1-l10n/WINNT_5.1_Clobber/mozilla/layout/html/table/src/nsTableFrame.cpp,
line 310]
nsTableOuterFrame::Destroy 
[c:/builds/tinderbox/Fx-Aviary1.0.1-l10n/WINNT_5.1_Clobber/mozilla/layout/html/table/src/nsTableOuterFrame.cpp,
line 82]
nsPositionedInlineFrame::Destroy 
[c:/builds/tinderbox/Fx-Aviary1.0.1-l10n/WINNT_5.1_Clobber/mozilla/layout/html/base/src/nsInlineFrame.cpp,
line 1103]
nsFrameList::DestroyFrames 
[c:/builds/tinderbox/Fx-Aviary1.0.1-l10n/WINNT_5.1_Clobber/mozilla/layout/base/src/nsFrameList.cpp,
line 129]
nsFrameList::DestroyFrames 
[c:/builds/tinderbox/Fx-Aviary1.0.1-l10n/WINNT_5.1_Clobber/mozilla/layout/base/src/nsFrameList.cpp,
line 129]
nsPositionedInlineFrame::Destroy 
[c:/builds/tinderbox/Fx-Aviary1.0.1-l10n/WINNT_5.1_Clobber/mozilla/layout/html/base/src/nsInlineFrame.cpp,
line 1103]
PresShell::Destroy 
[c:/builds/tinderbox/Fx-Aviary1.0.1-l10n/WINNT_5.1_Clobber/mozilla/layout/html/base/src/nsPresShell.cpp,
line 1868]


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