Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

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

  • 6 antwurd
  • 1 hat dit probleem
  • 3 werjeftes
  • Lêste antwurd fan 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.

Bewurke troch Simon Catesby op

Keazen oplossing

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

Dit antwurd yn kontekst lêze 👍 1

Alle antwurden (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

Keazen 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 :)