richard Reporter
	Description • 12 years ago

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20100101 Firefox/11.0
Build ID: 20120215222917

Steps to reproduce:

Firefox 11.0, Mac OSX 10.6.8, iMac 11,3, core i7, 8GB RAM

Saving current Firefox page 
  Command-P
  click PDF, click Save as PDF...
  select Desktop location for saved pdf file 
  scroll (mouse wheel) down to find desired folder on Desktop, open folder
  click Save and get Error Msg  script: chrome://xbl-marquee/content/xbl-marquee.xml:509 
or
  click Cancel and get Error Msg  script: chrome://xbl-marquee/content/xbl-marquee.xml:509

  


Actual results:

clicking Save or Cancel and get drop-down Error Msg appears (see attached screen shot)
  Warning: Unresponsive script
  script: chrome://xbl-marquee/content/xbl-marquee.xml:509

Hangs Firefox
Ignores both "Stop script" & "Continue" buttons in Error Msg window
Ignores all showing Firefox buttons: Save, Cancel 
Ignores all keyboard commands: Command-Q 
Shows but ignores all menu bar commands: Quit Firefox 

Does not interfere with any Mac OS commands outside of Firefox

use Force Quit...
select Firefox (which does NOT show "Not Responding" msg) & Force Quit button
Firefox quits as expected, all Firefox windows removed from screen
Restart Firefox, everything appears/functions OK
  until next Save to PDF in Print/Preview hangs Firefox
or 
  until a day or two of successful Save to PDF, 
  and then a Save to PDF hangs Firefox 
  with same error msg script: chrome://xbl-marquee/content/xbl-marquee.xml:509  
 


Expected results:

Save as PDF should have created a pdf file of viewed Firefox page and saved file in selected location

	Martijn Wargers (dead)
	Comment 1 • 12 years ago

I can't reproduce this. Is this on a particular page you are experiencing this?
Do you have any extensions installed? Does it happen in safe mode?

	Martijn Wargers (dead)
	Comment 2 • 12 years ago

Ok, I think you might be seeing bug 718542 here.

	Liz Henry (:lizzard Please n-i to RyanVM, jcristau, or pascal)
	Comment 3 • 11 years ago

Hi richard, it's been a while since anyone looked at the issue and I'm not able to replicate it. I'm going to close the bug as a duplicate as Martijn suggested. If you see it happen again, please re-open the bug and comment with more information. Thanks!