Terry R. wrote:
The date and time was Wednesday, April 01, 2009 3:48:20 PM, and on a whim, Peter Potamus the Purple Hippo pounded out on the keyboard:

Terry R. wrote:
The date and time was Monday, March 30, 2009 3:05:59 PM, and on a whim, Peter Potamus the Purple Hippo pounded out on the keyboard:

SM 1.1.15

Is anyone else having a similar problem:

you have something opened, like SM Mail. You click on compose, and you have to wait and wait and wait. The task manager says the program is not responding. After a minute, then the compose window opens and everything is back to normal, until you open something else. You could open the browser, or bookmark manager, or whatever, and you just wait.

I've tracked mine down to hostperm.1. If I close the program and remove it, then reopen and things work great again.

I've noticed the same problem with FF3. When I click to open it, it would take a few minutes. I could click on it again and a window would open. I would close that, and the original click would finally open. I removed permissions.sqlite and things would be back to normal.

So, anyone else having any similar problems?

I haven't noticed any issues with hostperm.1.

I have found that the constant sqlite updating of so many files in FF causes a lot more issues than it's worth IMO. I don't think most users need the repeated updating of the 6 files.

On one network I admin, all laptop users stopped using FF3 because the backup software wasn't configurable enough to exclude all the sqlite files, and the backup was constantly writing to the server and bogging down the performance. So it was a double whammy, constant sqlite updating and constant backing up. On another network, I was able to set up a FF profile in the backup software and exclude the sqlite files from updating constantly during the day, but have them backup once on shutdown.

Terry R.

so, from what you said, sqlite is the craps.

I hated it when FF took about 5 to 10 minutes to delete my SM bookmarks.

Yep. I was told when I filed a bug that sqlite is much more reliable, and the bug was filed as "WON'T FIX".

It was reliable for me the old way, because I know how to protect valuable data. I don't need a program writing to disk all freakin day to keep my cookie info updated, nor my history or bookmarks. What a waste of CPU cycles.

Terry R.

thats what I've been complaining about in the SM group for a long time. But the excuse I keep getting is the code is old and nobody knows how it works. Well, they're keeping the bookmarks in html format. Atleast thats a start.

*IMPORTANT*: Sorry folks, but I cannot provide email help!!!! Emails to me may become public

Notice: This posting is protected under the Free Speech Laws, which applies everywhere in the FREE world, except for some strange reason, not to the mozilla.org newsgroup servers, where your posting may get you banned.

Peter Potamus & His Magic Flying Balloon:
support-seamonkey mailing list

Reply via email to