 |
EDITOR NOTES
Note: Safari Cookies now requires SIMBL (for Snow Leopard 64-bit support), please make sure you backup your Favorites, and run the uninstaller, before installing the 1.0 update.
DESCRIPTION
Safari Cookies is the only cookie manager built for Mac OS X 10.5+ to integrate directly into Safari, for minimum disruption to your browsing experience. Localized for English, French, German, Italian and Spanish.
WHAT'S NEW
Version 1.3.7:
- Hopefully fixed SIMBL installer for 32bit Intel
REQUIREMENTS
Mac OS X 10.5 or later.
| SCREENSHOT
|
|
 |
|  |
 | |  |
| Safari Cookies User Reviews (86 posts) | Write A Review |
 | Jan 13 2010 |
CCWEBSURFER Safari Cookies integrates right into the Safari preferences which I was looking for. Using Safari Cookies allows me to preserve all my banking, financial and regular secured website cookies and clean out all the rest. I received excellent support from the developer for one minor setup issue related to my specific environment.
(Version 1.3.7) | |
| [ Reply ] | |
 | Jan 5 2010 |
REDDOG99 App worked well but Safari became slow to respond after I installed this. It was as if the cpu was bogging down. But I doubt that was the cause as I have an 8-core Mac Pro. Safari perked back up after I uninstalled the app. Maybe the combination with Glims & Adblocker was too much?
(Version 1.3.6) | |
| [ 1 Reply - Reply ] | |
Replies:
 | Jan 5 2010 |
PSYCHOS I'm running the same combo (Glims and Safari AdBlocker with Safari Cookies), and have had absolutely no problems with Safari being "slow to respond." The fact that you're on an 8-core Mac Pro doesn't really mean much; it's quite possible something else is slowing things down and you're bottlenecked on disk/swap or network or whatever instead. Just adding more cores doesn't do anything past helping CPU bottlenecks. This latest build (1.3.6) is looking much better so far in regards to fixing the major memory leaks I've had to date, although I haven't run it long enough to safely say whether or not that's the case. (Hoping it is the case, since this is a solid 5 star plugin all the way if it's not leaking anymore! Thanks again to the dev for all the hard work on trying to get the leaks fixed.)
(Version 1.3.6) | |
| Dec 30 2009 |
AESCHYLUS The memory leak is still not fixed, sorry to say. I have Glims and ClickToFlash installed, and normally my Safari is also around 300 Mb - 350 Mb of real memory, with slightly more Virtual Memory in use. Today I installed Safari Cookies, everything seemed fine, and I left my computer for an hour. When I returned, the screensaver was on and I needed to enter the password. Something seemed amiss, as I could not type in the box to enter my password for a few minutes. Then, I was able to see my desktop and the open Safari tab even before entering the password. Not right. I checked the memory usage, and real memory usage was 550 Mb and virtual memory usage was 1.6 Gb. Wow. Needless to say, this must be fixed before I can use Safari Cookies. Too bad, because it was so good getting rid of all those unwanted cookies when I first started Safari. Please keep working on this problem so, as there is a real need for this program.
(Version 1.3.4) | |
| [ 7 Replies - Reply ] | |
Replies:
 | Dec 30 2009 |
BOLLYWOOD I have another version, ill release which fixes a couple other leaks i found. give that one a spin and let me know how it goes. 1.3.5. just give me around half an hour to package it up.
(Version 1.3.4) | |
| Dec 30 2009 |
BOLLYWOOD 1.3.5 is available on my site: http://sweetpproductions.com/safaricookies/
(Version 1.3.4) | |
| Dec 31 2009 |
AESCHYLUS Thanks for the update. A few hours of using with Safari, and the RAM usage is still 220 MB, which is a real improvement over 1.3.4. Of course, I've got my fingers crossed and I'm hoping this will continue. (Other plugins still installed). I'm happy to be able to remove unwanted cookies, but I'm even happier to be able to easily remove those d*m! flash cookies.
(Version 1.3.5) | |
| Dec 31 2009 |
BOLLYWOOD Let me know how it works. Im pretty sure i found all the leaks........
(Version 1.3.5) | |
| Jan 5 2010 |
PSYCHOS Still leaking for me. Safari was up for ~4 days, real memory usage was around 1GB, and another 2GB of swap, which freed when I quit Safari. Running Glims and Safari AdBlocker too. Similar usage for a similar length of time with just those enabled and Safari Cookies off generally has Safari hovering around 400 - 500MB of real memory and very little swap. (In fact, I generally don't swap at all unless Safari Cookies is enabled, with any of the regular apps I use...) I've tried with just Safari Cookies with previous versions, and it eats up RAM as well, though I haven't tried that with 1.3.5.
(Version 1.3.5) | |
| Jan 5 2010 |
BOLLYWOOD Ive just uploaded 1.3.6 which XCode, and Instruments both say is Leak-Free.....
(Version 1.3.5) | |
| Jan 7 2010 |
PSYCHOS Finally seems to be better with 1.3.6, thanks! With moderate usage of Safari for a couple days, it's at 288MB of real memory used and no swap used by Safari. With previous builds, I would have expected to be at 500 - 800MB of real memory with a bunch of extra swap by this point.
(Version 1.3.6) | |
| Dec 15 2009 |
JOHNNY2BAD Had to uninstall it after about one hour. Opening a new window or tab caused Safari to freeze in an unrecoverable state. Force Quit, regardless of how it was invoked, did nothing. CPU usage grew to 100% and stayed pegged there ... forever. Through the use of the Console and Process Viewer, it seems that there was an application crash (Safari) and CrashReporter would then also crash. That is a huge problem, because you cannot prevent CrashReporter from launching. You can force quit the process, but it automatically respawns in 1 second if there is a crash active on the system. A hard restart is the only way to recover your Mac. After removing Safari Cookies v1.3.3 via the Safari: Preferences: Safari Cookies panel, Safari once again acts normally. I don't have any of the Safari add-ons mentioned by the developer as "usual suspects" but I do have two things in Safari that are non-standard: A CSS based ad-blocker and ClickToFlash. I am willing to live without neither, so Safari Cookies must go.
(Version 1.3.3) | |
| [ 1 Reply - Reply ] | |
Replies:
| Dec 16 2009 |
MACUPDATE ADMIN http://www.stlyrics.com/lyrics/hardertheycome/johnnytoobad.htm Sorry, I could not help myself.
(Version 1.3.3) | |
| Dec 6 2009 |
MACTECHHEAD You have a great idea and theory Russell Gray But alas for me Safari Cookies is a no-go. Anything that I have ever used on my Mac that required SIMBL has been nothing but trouble. Hope you'll reconsider dropping the requirement for SIMBL because as it is now. I'd rather not risk crashes or waiting for SIMBL updates after every update to Safari.
(Version 1.3.2) | |
| [ Reply ] | |
| Dec 2 2009 |
PSYCHOS I've found Safari Cookies to be a wonderful add-on, especially the auto-removal of cookies from sites that aren't in my history/bookmarks anymore. However, Safari Cookies is now causing Safari to take massive amounts of RAM. I'm also running Glims and Safari AdBlocker, both 64-bit under 10.6. With just those two enabled, Safari tends to grow to around 300MB - 350MB of active RAM at the most and stay there long-term. If I enable Safari Cookies, Safari keeps growing without bounds. When I finally decided to uninstall it, Safari was using 1.75GB of RAM, plus there was 1.5GB of swap in use that was freed when I quit Safari. With Glims and Safari AdBlocker, Safari doesn't eat into swap at all. I've tried with Glims and Safari AdBlocker disabled, and the same behavior persists. I tried turning off auto-manage temporarily, but that didn't help. Any ideas?
(Version 1.3.1) | |
| [ Reply ] | |
| Nov 11 2009 |
HUTCHBAY Doesn't work on my Safari 4.0.4 on OS X 10.5.8. After installation, I see a Cookies item in Safari Preferences, but when I click that I get the perma-beachball and Safari eventually crashes. Nice theory.
(Version 1.3.1) | |
| [ 3 Replies - Reply ] | |
Replies:
| Nov 12 2009 |
BOLLYWOOD What other plugins do you have installed? Glims, SafariStand, SafariSource.... and if you do a search for Safari Cookies, in console.app: /Applications/Utilities/Console.app what do you see?
(Version 1.3.1) | |
| Nov 27 2009 |
KEMENG Same Beachball effect. SafariStand, and Glims installed.
(Version 1.3.1) | |
| Nov 27 2009 |
- I removed all installed plugins (Glims, Stand, SafariBlock) but I got beachball effect - No console message:(
(Version 1.3.1) | |
| Oct 31 2009 |
DAVID210 I've had major issues running Safari Cookies on my MacBook Pro intel on 10.5.8 - thanks to a comment from the developer I tried getting rid of SafariStand 4.0L168 and I finally got SC back! Still don't understand why the latest version of SafariStand for Leopard didn't play nice with SC on Intel but worked fine on my 10.5.8 PPC machine? Doesn’t really matter in the end - Safari Cookies is much more valuable. Thanks for a great cookie manager!
(Version 1.3.1) | |
| [ Reply ] | |
| Oct 30 2009 |
LOUNGE DELUXE Again when updating from within Safari I get this error message: "Update Error! An error occurred while extracting the archive. Please try again later.". I think SafariCookies is a terrific 'plugin' and I can't imagine my computer life without it, and I don't mind downloading the update and installing it manually, but what's the point of an integrated update function when it doesn't work? SC is freeware so I'm not blaming the dev in any way, I'm just expressing my wish for a fix of this error.
(Version 1.3.1) | |
| [ 3 Replies - Reply ] | |
Replies:
| Oct 30 2009 |
BOLLYWOOD which version were you updating from?
(Version 1.3.1) | |
| Oct 31 2009 |
LOUNGE DELUXE Version 1.2 (I send you an email about it on October 18), but it happened again when going from 1.3 to 1.3.1.
(Version 1.3.1) | |
| Oct 31 2009 |
LOUNGE DELUXE After restarting Safari in 64-bit mode instead of 32-bit SC updates fine within Safari, so problem solved. Would be a good thing if the dev makes a note of this on his website and the info section on MU.
(Version 1.3.1) | |
| Oct 29 2009 |
PAULMREIZ Just a mere technicality, but isn't the statement "Cookie manager integrates directly into Safari" misleading now that SIMBL is a requirement? Safari Cookies used to be my cookie manager of choice before Snow Leopard and the SIMBL requirement.
(Version 1.3.1) | |
| [ 3 Replies - Reply ] | |
Replies:
| Oct 29 2009 |
BOLLYWOOD Apart from building a background process that sits around waiting for Safari to open. SIMBL is the only way to get this working. in fact SIMBL is already doing exactly that..... Glims, and 1Password have their own background processes running. So the more Plugins you have installed, the more background daemons your computer is going to need. Seeing as how, a lot of other plugins are utilising the 'sniffing' SIMBL is doing, it makes sense to use it. And, to be honest, i would like to have as few processes running as possible.
(Version 1.3.1) | |
| Oct 29 2009 |
don't blame the devs..... complain to Apple, and ask for an officially supported plugin architecture!
(Version 1.3.1) | |
| Oct 29 2009 |
PAULMREIZ Not pointing blame or even questioning your logic and use of SIMBL. Just pointing out that this is not a "direct" Safari cookie manager any more, and that you should consider changing the description.
(Version 1.3.1) | |
|
| View all 86 posts >> |
|
