Αυτός ο ιστότοπος θα έχει περιορισμένη λειτουργικότητα, όσο εκτελούμε εργασίες συντήρησης για να βελτιώσουμε την εμπειρία σας. Αν ένα άρθρο δεν επιλύει το ζήτημά σας και θέλετε να κάνετε μια ερώτηση, η κοινότητα υποστήριξής μας είναι έτοιμη να σας βοηθήσει στο Twitter (@FirefoxSupport) και στο Reddit (/r/firefox).

Avatar for Username

Αναζήτηση στην υποστήριξη

Προσοχή στις απάτες! Δεν θα σας ζητήσουμε ποτέ να καλέσετε ή να στείλετε μήνυμα σε κάποιον αριθμό τηλεφώνου ή να μοιραστείτε προσωπικά δεδομένα. Αναφέρετε τυχόν ύποπτη δραστηριότητα μέσω της επιλογής «Αναφορά κατάχρησης».

Μάθετε περισσότερα

Αυτό το νήμα αρχειοθετήθηκε. Παρακαλούμε κάντε νέα ερώτηση αν χρειάζεστε βοήθεια.

Why does FF 53.0.2 crash when I want to use the "Open File..." (Ctrl+O) command thrice?

  • 2 απαντήσεις
  • 1 έχει αυτό το πρόβλημα
  • 6 προβολές
  • Τελευταία απάντηση από cor-el

TPPN
TPPN
more options

These are the first things I do after booting my computer from a clean live CD with Tahrpup 6.0.5 OS: I update the OS. I update the the package manager. I use the package manager to download and install Firefox 32.0.3 . i use FF32.0.3 preference tab to make "Welcome to Firefox" and "Mozilla Firefox Star" tabs the pages to be opened when I start FF. I use the FF Menu Bar → File/Open File ... command to find and open in the third tab a .html file I have built. I use the FF Menu Bar → File/Open File ... command to find and open in the fourth tab another .html file I have built. i use FF32.0.3 preference tab to make "Welcome to Firefox" and "Mozilla Firefox Star" tabs and the 2 tabs with .html files I have buit the 4 pages that will be opened when I start FF. I set the "New tab" controls to open in a blank page. I upgrade FF32.0.3 to 53.02 I use FF Menu Bar → File/ but when I click on "Open File... " , Firefox crashes.

Opening files from the browser is very important for me.

How can I make the "Open File..." command (that worked flawlessly before upgrading to version 53.0.2) stop crashing FF's updated version?

PS: Modifications were made to correct typos and misspellings.

These are the first things I do after booting my computer from a clean live CD with Tahrpup 6.0.5 OS: I update the OS. I update the the package manager. I use the package manager to download and install Firefox 32.0.3 . i use FF32.0.3 preference tab to make "Welcome to Firefox" and "Mozilla Firefox Star" tabs the pages to be opened when I start FF. I use the FF Menu Bar → File/Open File ... command to find and open in the third tab a .html file I have built. I use the FF Menu Bar → File/Open File ... command to find and open in the fourth tab another .html file I have built. i use FF32.0.3 preference tab to make "Welcome to Firefox" and "Mozilla Firefox Star" tabs and the 2 tabs with .html files I have buit the 4 pages that will be opened when I start FF. I set the "New tab" controls to open in a blank page. I upgrade FF32.0.3 to 53.02 I use FF Menu Bar → File/ but when I click on "Open File... " , Firefox crashes. Opening files from the browser is very important for me. How can I make the "Open File..." command (that worked flawlessly before upgrading to version 53.0.2) stop crashing FF's updated version? PS: Modifications were made to correct typos and misspellings.

Τροποποιήθηκε στις από το χρήστη TPPN

Όλες οι απαντήσεις (2)

FredMcD
FredMcD
more options

In the address bar, type about:crashes<enter>. Note: If any reports do not have BP- in front of the numbers/letters, click it to submit them.

The crash report is several pages of data. We need the report numbers to see the whole report.

Using your mouse, mark the most recent 7 - 10 crash reports, and copy them. Press the Reply button. Now go to the reply box and paste them in.

aboutcrashesFx29

For more help on crash reports, see; https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support

Some of your crash reports weren’t sent to the Mozilla Servers.

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Try to reset download prefs on the about:config page to see if that has effect or delete prefs.js in the profile folder to reset all prefs.

Create a new profile to test if your current profile is causing the problem.

See "Creating a profile":

If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.