This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search 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.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

OS X Mojave (full release) - FF freezes if trying to rename a file to save

  • 6 antwoorde
  • 1 het hierdie probleem
  • 1 view
  • Laaste antwoord deur Simon Catesby

more options

Firefox 62.0.2 (64-bit) OS X Mojave - 10.14 - live public full release (i.e. not the Beta) MacBook Pro, with menu bar

Example: Using Google, go to Images tab. Right click on an image and select "Save image as". If you click on the file name, as you want to change the name, FF freezes.

Not only does it freeze but right clicking on the icon in the Dock only shows "Quit" (not Force quit) and that does nothing. Furthermore, it locks you out from being able to use the Apple symbol (top left) to get to "Force quit" that way. Only solution I have found so far is a forced reboot (i.e. power off/on).

I can reproduce this every time.

If anyone wants more info just let me know what you want to know. I suspect that, given Mojave has only been live a few hours, that a lot more people might run into this in the coming days.

Firefox 62.0.2 (64-bit) OS X Mojave - 10.14 - live public full release (i.e. not the Beta) MacBook Pro, with menu bar Example: Using Google, go to Images tab. Right click on an image and select "Save image as". If you click on the file name, as you want to change the name, FF freezes. Not only does it freeze but right clicking on the icon in the Dock only shows "Quit" (not Force quit) and that does nothing. Furthermore, it locks you out from being able to use the Apple symbol (top left) to get to "Force quit" that way. Only solution I have found so far is a forced reboot (i.e. power off/on). I can reproduce this every time. If anyone wants more info just let me know what you want to know. I suspect that, given Mojave has only been live a few hours, that a lot more people might run into this in the coming days.

Gewysig op deur Simon Catesby

Gekose oplossing

as a followup: mozilla has now released an update to firefox which should fix this problem - Update Firefox to the latest release

Lees dié antwoord in konteks 👍 1

All Replies (6)

more options

Please try in : SAFE MODE

In Firefox Safe mode these changes are effective:

  • all extensions are disabled (about:addons)
  • default theme is used (no persona)
  • userChrome.css and userContent.css are ignored (chrome folder)
  • default toolbar layout is used (file: localstore-safe.rdf)
  • Javascript JIT compilers are disabled (prefs: javascript.options.*jit)
  • hardware acceleration is disabled (Options > Performance > Uncheck to view)
  • plugins are not affected
  • preferences are not affected

TEST''''is issue still there ?

If so : please try a Refresh but Note that this does more than uninstalling and re-installing does. Normal uninstalling does not remove some preferences which may have become corrupt. Please Refresh but do this 1st:

then

more options

Thanks for that Pkshadow.

I had done the restart with add-ons disabled, forgot to state that, sorry.

Hadn't done ther refresh thing though (didn't know about that).

Same result, freezes if I try to rename (an image file at least) when I go to save it.

(
more options

This looks similar to this macOS Mojave bug (please read Bugzilla etiquette before commenting in bug reports): Bug 1489785 [MacOS 10.14] Cannot choose where to download files or print because popup window always freeze

Other macOS Majave bugs are listed in meta bug 1466336. macOS 10.14 Mojave is a new OS and Mozilla developers are working on these issues.

more options

Yes, it does indeed look similar to that one Alice. It's not quite the same as I'm seeing but I very much suspect it's caused by the same module. Well found :)

more options

Gekose oplossing

as a followup: mozilla has now released an update to firefox which should fix this problem - Update Firefox to the latest release

more options

Thanks Philipp, that did indeed solve it :)