Closed Bug 166997 Opened 23 years ago Closed 23 years ago

Complete crash when printing an article

Categories

(Core :: Printing: Output, defect)

x86
Windows 98
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: viperc699, Assigned: rods)

Details

(Keywords: crash, stackwanted)

User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.1) Gecko/20020826 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.1) Gecko/20020826 I went to a printer friendly version of an article on today's WashingtonPost.com and it simply crashed right after I hit PRINT in the button bar. Reproducible: Always Steps to Reproduce: 1.Hit Print 2. 3. Actual Results: Crashed Expected Results: Printed an article Below is the details of the fault error I received. MOZILLA caused an invalid page fault in module KERNEL32.DLL at 0187:bff76846. Registers: EAX=005501d4 CS=0187 EIP=bff76846 EFLGS=00010246 EBX=005501d4 SS=018f ESP=00550000 EBP=0055001c ECX=005500a0 DS=018f ESI=81b43d84 FS=2faf EDX=bff76855 ES=018f EDI=005500c8 GS=0000 Bytes at CS:EIP: ff 55 18 83 c4 10 64 8f 05 00 00 00 00 c9 c3 8b Stack dump: 005500c8 005501d4 005500e4 005500a0 005501d4 bff76855 005501d4 005500b0 bff87fe9 005500c8 005501d4 005500e4 005500a0 bff76855 0055028c 81b43d84
MOZILLA caused an invalid page fault in module KERNEL32.DLL at 0187:bff76846. Registers: EAX=005501d4 CS=0187 EIP=bff76846 EFLGS=00010246 EBX=005501d4 SS=018f ESP=00550000 EBP=0055001c ECX=005500a0 DS=018f ESI=81b43d84 FS=2faf EDX=bff76855 ES=018f EDI=005500c8 GS=0000 Bytes at CS:EIP: ff 55 18 83 c4 10 64 8f 05 00 00 00 00 c9 c3 8b Stack dump: 005500c8 005501d4 005500e4 005500a0 005501d4 bff76855 005501d4 005500b0 bff87fe9 005500c8 005501d4 005500e4 005500a0 bff76855 0055028c 81b43d84
Did you submit a talkback report for the crash? Could you provide the talkback ID for the crash?
Keywords: crash, stackwanted
Summary: COMPLETE CRASH WHEN PRINTING AN ARTICLE → Complete crash when printing an article
what is the exact URL that crashes for you...
I printed 3 sub-articles at washingtonpost.com w/o crashing on win 98 system.
need testcase
Keywords: testcase
do you still crash with 1.3a or latest nightly build ?
Keywords: testcase
I tried a nightly Phoenix build (4/2/03) for the first time. I got a BSOD when trying to print this page: http://www.berkshire.net/~biancolo/2003/03/ Although I have never tried to print this page before, I thought it was the new build that was the problem. So I reverted to 0.5 milestone, cleared profile, etc. and got the same crash. So perhaps it's something page-specific. I have tried printing other pages successfully, and have even printed the first sheet of the problem page. But when I try to print the whole thing Win2K sp3 crashes (gets to about "processing 75%" and then blue-screens). I apologize for not trying this on Mozilla, but I'm on a dialup and I just can't download that big honker right now...
it is unlikely the crash at the berkshire URL is related to this bug. sounds like a new bug this bug is WORKSFORME due to complete lack of response for reporter
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Ah, I see. I was trying to avoid posting a duplicate so I grabbed the "crashes while printing" bug that looked closest. Whoops! Anyway, I'd be happy to keep an eye on the comments of the new bug and give you whatever information you need if you tell me which one it is. Thanks!
You need to log in before you can comment on or make changes to this bug.