* TITLE/SUMMARY Mac OS crashes upon printing from Gecko * STEPS TO REPRODUCE 0) Launch Apprunner 1) Go to any web page (I used www.prometheus-music.com, but only because it's my web site.) 2) From the file menu, select "Print". (While it shouldn't matter, I only printed the first page of the document.) * RESULT - What happened Upon becoming the active document in the print queue with a state of "Starting Job" the Finder freezes; mouse pointer can still be moved, but no interface objects respond. The first and fourth time I did this, it actually flat out crashed. (stack crawl enclosed from the first time; the fourth time, Macsbug was even broken!) (It does work, however, if you print the really simple Gecko Welcome page.) * REGRESSION - Occurs On Mac OS Apprunner (4.9.99 PM optimized build) - Doesn't Occur On Win32 Apprunner (4.9.99 AM optimized build [NT 4, Service Pack 3]) (didn't check Linux) * CONFIGURATIONS TESTED - [Mac] Power Mac 8500/120 (233 Mhz 604e), 64 MB RAM (VM on; 1 MB of VM used), 1024x768 (Thousands of Colors), Mac OS 8.5.1 - [Win32] Vectra VL (233 Mhz P2), 96 MB RAM, 800x600 (True Color), NT 4.0 SP3. - [Linux] Vectra VL (266 Mhz P2), 96 MB RAM. * STACK CRAWL PowerPC read-only memory exception at 0021B6DC GetIndSymbol+00680 (CurStackBase does not seem to apply...dumping 4K.) Calling chain using A6/R1 links Back chain ISA Caller 03DA1BB3 PPC 001FCBCC EmToNatEndMoveParams+00014 03DA1B40 PPC 00225534 FragRelease+0006C

Linux doesn't crash but after putting up all the dialogs and slowing down like it was printing, it doesn't. It does everything it should to print. It thinks it's printing, but you'll nevr get that document. On my Mac, not only did it crash hard (no debugger, no anything), it proceded to go into fits after restart. Only after the third crash after restart(I didn't do anything restart-->crash) was I presented with a dialog saying my desktop printer didn't have enough memory and would I like to temporarily increase the allocation, 'yes'-->crash-->restart-->'no' :-). Jan, are we still using [RN] or do i have to go find that bug? I would not wish this on anyone.

[Corrected bug title. Dunno who changed it, but as the bug report says, Seamonkey isn't crashing. Seamonkey is sending a print job to the Mac OS that is crashing the Mac OS.]

Print crash on Win 95 using 4/13 build in Apprunner. Here are details: APPRUNNER caused an exception 10H in module RAPTORHTML.DLL at 0137:018af6a5. Registers: EAX=000001d1 CS=0137 EIP=018af6a5 EFLGS=00010246 EBX=0076cd84 SS=013f ESP=0076cd10 EBP=0076cd24 ECX=00000000 DS=013f ESI=007d5618 FS=132f EDX=000001d1 ES=013f EDI=00000001 GS=0000 Bytes at CS:EIP: dd d8 5f 5e 5b c9 c2 0c 00 ff 74 24 10 ff 74 24 Stack dump: 0076cd84 018ef4d0 007d5564 00000000 00000000 0076ce00 018af274 007d55a8 00000000 00000000 007d6564 00000000 007d5564 00000002 00450978 00000000 Crashes are no consistent. Sometimes pages print.

To clarify previous 4/14 comments, printing crashes from the menu item 'Print'. The 'Print' icon does not work.

Re: "the 'Print' icon doesn't work" see bug 4959

dcone, I would really like to put this one on the M5 radar, ok? If we can't get printing to work for M5, it should at least not crash...cool?

This was crashing on background only, this has been fixed. pixelType on the source bitmap was incorrect.

VERIFIED fixed for MacOS AND Linux with 1999042608 builds