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

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Starting Firefox triggers Memeo backup and Trusteer to run and bog down cpu

  • 4 uphendule
  • 0 zinale nkinga
  • 7 views
  • Igcine ukuphendulwa ngu lewis.heilig

more options

Hello, While not on every occurrence of starting Firefox, too many times Firefox won't bring up its home page (Google) because two applications running in the background (Memeo Premium Backup and Trusteer Rapport) start to run at the same time and contribute at least 70% of the CPU load, with Firefox accounts for another 20%.

I imagined that Google is flooding Firefox with a lot of files that Memeo begins tabulating for transfer in anticipation of its external backup drive being eventually switched on.

So I decided to tell Memeo to specifically exclude two system folders which might be storing temporary files when Firefox is active.

C:\Users\**\AppData\Roaming\Mozilla\Firefox C:\Users\**\AppData\Local\Mozilla\Firefox

Doing this did not improve things, as Memeo and Trusteer occasionally turn on as Firefox is starting up.

Does anyone know of any other folders which could be potential locations for temporary data that Memeo may feel obligated to interact with.

Thanks

Hello, While not on every occurrence of starting Firefox, too many times Firefox won't bring up its home page (Google) because two applications running in the background (Memeo Premium Backup and Trusteer Rapport) start to run at the same time and contribute at least 70% of the CPU load, with Firefox accounts for another 20%. I imagined that Google is flooding Firefox with a lot of files that Memeo begins tabulating for transfer in anticipation of its external backup drive being eventually switched on. So I decided to tell Memeo to specifically exclude two system folders which might be storing temporary files when Firefox is active. C:\Users\**\AppData\Roaming\Mozilla\Firefox C:\Users\**\AppData\Local\Mozilla\Firefox Doing this did not improve things, as Memeo and Trusteer occasionally turn on as Firefox is starting up. Does anyone know of any other folders which could be potential locations for temporary data that Memeo may feel obligated to interact with. Thanks

All Replies (4)

more options

I'm not familiar with Memeo, but does it have any kind of log showing what it backed up recently?

Trusteer (or Rapport) from IBM is a program that some banks require to make your browser connections more secure. Do you have a Trusteer add-on installed in Firefox that may be connecting with the external program?

more options

jscher2000 - Support Volunteer said

I'm not familiar with Memeo, but does it have any kind of log showing what it backed up recently? Trusteer (or Rapport) from IBM is a program that some banks require to make your browser connections more secure. Do you have a Trusteer add-on installed in Firefox that may be connecting with the external program?

Thank you for your reply. Both manufacturers Seagate and Western offer backup software products bundled with some of their external drives. Memeo is a similar product from a third party.

I did find some log files associated with Memeo, but the creation date of the most recent log file is 2AM this morning, and my latest Firefox/Memeo incident occurred this afternoon.

There is an add-on for Trusteer in Firefox, and my Firefox home page (Google.ca) is a website flagged for protection by Trusteer, so as soon as this page opens up, Trusteer might have a good reason to become active.

Memeo is not configured to back up any of the Trusteer files. But that doesn't mean that Firefox and/or Trusteer are not causing Memeo to work hard. Every time Windows creates/updates a file, whether due to Firefox or Trusteer, Memeo gets called to determine if that file should be scheduled for being backed up eventually to the external drive. If a particular file created by Firefox or Trusteer gets deleted when Firefox closes, then Memeo has to be called again to remove that file from its list of files to be backed up.

One other thing that I can do is to switch to using a different browser the next time Firefox stalls at startup. If the other browser doesn’t stall while opening Google.ca, then that means that Firefox has a greater impact on Memeo than say Chrome or Edge.

more options

Does Memeo let you see the queue of files that it thinks changed?

You could also find the Mozilla folder(s) in the hidden folder

C:\ProgramData

and exclude those as well. I think that is where updates are stored before installation, and you don't need to back those up.

more options

jscher2000 - Support Volunteer said

Does Memeo let you see the queue of files that it thinks changed? You could also find the Mozilla folder(s) in the hidden folder C:\ProgramData and exclude those as well. I think that is where updates are stored before installation, and you don't need to back those up.

When the external backup drive gets plugged in and Memeo begins dumping files to it, its flakey GUI will display some of, but not all of the files that it is backing up.

Very few of those files appear to be related to Firefox, as there are only about a dozen .sqm files that get backed up. The reason for so few Firefox related files being backed up could be that Firefox deletes most of the files that it creates when the browser closes, so Memeo no longer thinks that it has anything to back up.

Memeo does not let me know that it has taken notice of a file that has been created or updated or deleted.

The C:\Program Data folder is already excluded for backup by Memeo and I can't tell how much activity is occurring within this folder as Firefox starts up.

In my daily routine of creating emails, updating documents, and spreadsheets, the traffic that I generate is low over any time span.

But when I fire up a browser, the mechanics of doing so can easily result in many files being written in a short period of time, so Memeo will be loaded up with a lot of work to do within a matter of seconds.

All my browsers (Firefox, Chrome, and Edge) load the Google search engine as the home page and in all of these cases, these home pages are protected by Trusteer Rapport, so Rapport introduces an additional layer of activity to burden the CPU with.

Firefox is the worse offender of the 3 browsers, in terms of triggering a chain reaction of heavy CPU use.

Today, I filed a report with Trusteer to ask their opinion as to how their extension reacts to Firefox starting up with a protected website.

Thanks for your suggestions.