Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Learn More

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

Bookmarks restore takes literally hours to finish

  • 2 risposte
  • 2 hanno questo problema
  • 1 visualizzazione
  • Ultima risposta di John99

more options

My bookmark back json files are about 3.5 MB. If I open bookmarks and then restore to a file (or a previous day, doesn't make a difference), then it hangs a little and gives me the message that there's an unresponsive script. That has to do with the processing for restoring the bookmarks apparently, so fine. I click to ignore these messages and continue. Then I wait and wait.

I've discovered that if I leave it for 8 hours it will finish. I've checked it after about 2 hours and it's definitely not finished. How can it possibly be taking this long? I guess I can try to live with it...

A related problem is that Firefox Sync only takes about 10 minutes to destroy my bookmarks. How do you begin setup with Sync and use the option to replace the local set? I know how to do this once it's already set up, but I can't find the option during setup for a computer. It starts syncing right away, and this generally causes collisions because the computer contains a similar, but slightly older and reorganized set of bookmarks. I don't know how to do this process without corrupting my bookmarks on the server. Now I need to start the sync and replace the server set with a local set.. well, in a day or so once a computer is able to restore to the correct set.

Is the only way to replace the computer's bookmarks with the server bookmarks for an as-of-yet unsynced computer to delete all bookmarks? Correspondingly, is the only way to replace the server data from a as-of-yet unsynced computer to to clear the data first?

My bookmark back json files are about 3.5 MB. If I open bookmarks and then restore to a file (or a previous day, doesn't make a difference), then it hangs a little and gives me the message that there's an unresponsive script. That has to do with the processing for restoring the bookmarks apparently, so fine. I click to ignore these messages and continue. Then I wait and wait. I've discovered that if I leave it for 8 hours it will finish. I've checked it after about 2 hours and it's definitely not finished. How can it possibly be taking this long? I guess I can try to live with it... A related problem is that Firefox Sync only takes about 10 minutes to destroy my bookmarks. How do you begin setup with Sync and use the option to replace the local set? I know how to do this once it's already set up, but I can't find the option during setup for a computer. It starts syncing right away, and this generally causes collisions because the computer contains a similar, but slightly older and reorganized set of bookmarks. I don't know how to do this process without corrupting my bookmarks on the server. Now I need to start the sync and replace the server set with a local set.. well, in a day or so once a computer is able to restore to the correct set. Is the only way to replace the computer's bookmarks with the server bookmarks for an as-of-yet unsynced computer to delete all bookmarks? Correspondingly, is the only way to replace the server data from a as-of-yet unsynced computer to to clear the data first?

Tutte le risposte (2)

more options

It sounds like a problem related to hardware acceleration.

Please review the articles listed below to see if they are able to help you out in any way:

--

Please note that if hardware acceleration is disabled, the appropriate step might be to active it.

more options

Install and run the add-on places maintenance (from a Firefox developer). It is unlikely to do any harm and may fix the problem.

Afterwards note the add-on does have an option to produce a statistics report, use that option and paste the results into your next post.