Really slows down Chrome. I've had been using it for years, but after setting up Chrome to reload about 10 pages, Chrome was very slow to load after a restart. I removed GlimmerBlocker, and I'm now encountering no problems. Perhaps this is a Chrome issue, or simple incompatibility. However, GlimmerBlocker has lost its usefulness for Chrome users.
Since launch of 2.0, and even in the current 2.1 beta versions, there is a bug that continually generates error messages in logs. These logs can easily build up to many gigabytes in size on the hard drive, and need some expertise to delete as they are hidden. I found 20 GB of these logs on my hard drive.
Therefore, I do not recommend Camino 2 until, and if, this is fixed.
I have been using Camino for years as my main browser, but I am now forced to revert to Safari and Firefox. Camino 1.x.x is no longer being supported and may have huge security holes.
The error in question that will repeat every second in logs:
[0x0-0x33033].org.mozilla.camino[554] Macintosh-2.local Camino[554] : kCGErrorIllegalArgument: CGSGetWindowBounds: NULL window
I have confirmed ENRO's comment above by downloading the nightly build (these can be extremely unstable or not work with plugins you may have installed, so I do not recommend people use them).
Camino 2 has been out for 2 weeks short of a year, and the first report of the bug was in January. An issue as serious as this should not take 10 months to resolve. For a serious problem, even in the open source world, that lag is unacceptable.
Until the next official release that incorporates the fix, my advice remains for typical user: steer clear.
This can recover files from reformatted disks, but the rename feature is worthless. After recovering the files (named as 1,2,3, etc), it is supposed to dig into the file to determine the original name and reset it to the original. The software just stops working, forcing you to either force it to quit (which often doesn't work) or force the computer to restart.
Renaming bogs down at File 1. This is very expensive software for what you're getting. I was able to recover files using cheap PC shareware (on a Mac formatted disk) that did the exact same thing. If this worked as advertised, it would be wonderful. FileSalvage, unfortunately, is mostly snake oil.
[Version 5.1]
There are currently no troubleshooting comments by this member.
Please login or create a new MacUpdate Member account to use this feature
GlimmerBlocker
Betaiii reviewed on 09 Jul 2011
+1
Camino
However, it is currently crippled.
Since launch of 2.0, and even in the current 2.1 beta versions, there is a bug that continually generates error messages in logs. These logs can easily build up to many gigabytes in size on the hard drive, and need some expertise to delete as they are hidden. I found 20 GB of these logs on my hard drive.
Therefore, I do not recommend Camino 2 until, and if, this is fixed.
I have been using Camino for years as my main browser, but I am now forced to revert to Safari and Firefox. Camino 1.x.x is no longer being supported and may have huge security holes.
Reference: https://bugzilla.mozilla.org/show_bug.cgi?id=541897
+1
[0x0-0x33033].org.mozilla.camino[554] Macintosh-2.local Camino[554] : kCGErrorIllegalArgument: CGSGetWindowBounds: NULL window
+1
Camino 2 has been out for 2 weeks short of a year, and the first report of the bug was in January. An issue as serious as this should not take 10 months to resolve. For a serious problem, even in the open source world, that lag is unacceptable.
Until the next official release that incorporates the fix, my advice remains for typical user: steer clear.
FileSalvage
BetaIII reviewed on 04 Mar 2007
Renaming bogs down at File 1. This is very expensive software for what you're getting. I was able to recover files using cheap PC shareware (on a Mac formatted disk) that did the exact same thing. If this worked as advertised, it would be wonderful. FileSalvage, unfortunately, is mostly snake oil.