MacUpdate: Member Profile

Brilormac

Downloads: 2

Posts: 15

Smile Score: +17

About Me

I am a Free member
Gender: Male
Mac Software Engineer

Visit Stats
Last Visit: 65 days ago
Member Since: 23 Jan 2008
Profile Views: 715

Website
http://members.cox.net/ccnx

PreMinder 1.5.5
(Shareware)

MainMenu Pro 3.0.5
(Shareware)

Brilormac's Posts

Average Rating from Brilormac:

(2)

sort: smiles | time

iFreeMem

Brilormac commented on 01 Jun 2011

If Developer tools are installed, go to a Terminal window and type purge. The cost: FREE. There are free wrappers for the purge command ( I wrote one ).

[Version 1.0]

iMemoryCleaner

Brilormac commented on 01 Jun 2011

If Developer tools are installed, just go to a Terminal window and type purge. It will purge all inactive memory. Cost: FREE. There are freeware wrappers for purge too.

[Version 1.0]

Screen Shades

Brilormac reviewed on 06 Sep 2010

Leak detection using Apple's Instruments tool shows this to have multiple leaks in "rbframework.dylib" ( these are frameworks written by Monkey Bread Software for RealBasic developers - which is the IDE used to develop Screen Shades ). Specifically, the responsible frames are:
LoadPlugins, REALSetPropValueCFStringRef and AddRelocEntry. There are multiple leak occurrences for all of these. This means the memory used by this program will increase the longer it runs.

The developer of Screen Shades should consider using an alternative method since the used framework leaks ( and would have no control over it since presumably the developer of Screen Shades is not the same developer of the framework that leaks ).

One app in this category that does not leak is SmartSaver( and I am NOT the developer of this app ).

[Version 1.0]

Shades

Brilormac reviewed on 24 Jul 2010

While Shades does do the job, relatively speaking it is a resource hog.

For an app with no UI, it uses 28 to 29 MB of real memory ( as shown in Activity Monitor ). I have several apps with multiple window UIs with real memory usage at 8 to 10 MB. Moreover, the memory usage grows the longer Shades runs. This is a memory managements issues. See leaks below.

Also, the code is leaking memory. A quick analysis with the "leaks" command line tool ( via Terminal ) on the running Shades ( had been running for approximately an hour ) shows 37 leaks for 2432 bytes. This keeps accumulating the longer the Shades app runs. A similar analysis with Instruments confirms.

This doesn't make Shades a bad app, just one that needs improving ( the Finder in OS X 10.6.4 leaks too ). This would be a 5 star rating except for the leaks and bloated memory usage.

[Version 1.2b3]

There are currently no troubleshooting comments by this member.

Displaying 1-4 of 4

Please login or create a new
MacUpdate Member account
to use this feature

Add/Update Listing About MacUpdate Desktop Career Opportunities RSS Twitter Facebook Advertise Sitemap