Dette websted vil have begrænset funktionalitet, mens vi gennemgår vedligeholdelse for at forbedre din oplevelse. Hvis en artikel ikke løser dit problem, og du vil stille et spørgsmål, har vi vores supportfællesskab, der venter på at hjælpe dig på @FirefoxSupport på Twitter og/r/firefox på Reddit.

Søg i Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Læs mere

Firefox crashes

  • 1 svar
  • 1 har dette problem
  • 1 visning
  • Seneste svar af dmcdon

more options

Modal race condition requiring force quit of app


If you save a web page to disk using the "File->Save Page As" function and there is no internet connection (or the server doesn't respond) and you then try to save another page to disk using the same procedure (open in another tab), the file requester for the second page save will start to appear but if the timing for the previous page save is just right (or bad...) then a "Download Error" (<local filepath> could not be saved, because the source file could not be read." error dialog will appear as the file requester is coming up.

As the error dialog is modal and the file requester is modal and both are now on the screen at the same time then user input is blocked requiring a "force quit" of the app using "Apple->Force Quit..."

'''Modal race condition requiring force quit of app''' If you save a web page to disk using the "File->Save Page As" function and there is no internet connection (or the server doesn't respond) and you then try to save another page to disk using the same procedure (open in another tab), the file requester for the second page save will start to appear but if the timing for the previous page save is just right (or bad...) then a "Download Error" (<local filepath> could not be saved, because the source file could not be read." error dialog will appear as the file requester is coming up. As the error dialog is modal and the file requester is modal and both are now on the screen at the same time then user input is blocked requiring a "force quit" of the app using "Apple->Force Quit..."

Alle svar (1)

more options

This would be better as a bug report as it's clear what's going wrong. It's not a crash as such as they're both just waiting for each other while blocking input.

Ændret af dmcdon den