That said, the vast majority of OS X apps will link against the WebKit framework; not just Safari, but also Adium, Tweetbot, Mail.app, Growl, Notes, TextMate, iTunes, etc. It's pretty much guaranteed that it's in memory already, so there's no harm linking against it.
As for memory, ps reports about 64 MB of RSS; Activity Monitor reports 47.5 MB of memory used. Seems okay to me.
Which version of Mac OS are you using?
First, linking with the webkit framework is not the problem, using the framework is. I was playing around with preferences and also location. As you say, this is when the Webkit frameworks kicks in, which might explain the memory blowup to 118MB.
Second, I seem to recall that modern OS allocators are reluctant to release memory back to the OS (pool) unless required (when available memory is low) hence the process appears to use more memory than what it actual might be using. When I just restart Flux without fiddling with preferences, memory usage stays at around 45MB. I still think this is way too high if you think about what the program is doing, but given the above, even if Activity Manager reports that Flux is using 45MB, it might not really use 45MB now, only at some point.
I remember I used Xcode's instruments to investigate my program and could then see that the real active memory used by the process was usually much less than what Activity Manager, top, and ps w/friends were reporting. So a large part of the memory the process is currently holding (45MB) might be released back to the OS if needed, I think. If someone has more details on this, please elaborate.
Edit: Flux is also running with 4 threads(!) which of course also adds to the process memory usage. Isn't a thread stack around 4-8 MB?
Also, Flux appears to use 0.1% CPU continuously which is sloppy since CPU usage can be remedied by putting (nano)sleep in the poll cycle to make it use zero CPU.
Although on my Mavericks MBP, it's currently using 10.4MB (0.13%) of "Real Mem" according to Activity Monitory.
It's command-line, like the Linux version, which means it's very lightweight. It's using 0% CPU (looks like 4 seconds of CPU over the last week or two), but it does seem to use 111 MB memory -- I'm curious why and might poke at it. (Yay free software.)
wyvern:~/src/redshift/redshift-1.7/src gthomas$ otool -L redshift redshift: /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics (compatibility version 64.0.0, current version 600.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
First, the latest patched version can be found at https://github.com/geofft/redshift
You may need autoconf, automake, and gettext. I used homebrew. I also had to run
ln -s /usr/local/opt/gettext/bin/autopoint /usr/local/bin
to get the autopoint build-time dependency.To get redshift to run at login, we'll use launchd. Save the following as ~/Library/LaunchAgents/redshift.plist (modify as needed if your binary and config files are elsewhere).
<plist version="1.0">
<dict>
<key>Label</key>
<string>redshift</string>
<key>RunAtLoad</key>
<true />
<key>Program</key>
<string>/usr/local/bin/redshift</string>
<key>OnDemand</key>
<false/>
<key>ProgramArguments</key>
<array>
<string>-c ~/.config/redshift.conf</string>
</array>
</dict>
</plist>
then run launchctl load ~/Library/LaunchAgents/redshift.plist
You can use launchctl list | grep redshift
to see that it's working. Thanks to http://developernotes.com/archive/2011/04/06/169.aspxwow64cpu.dll!TurboDispatchJumpAddressEnd+0x6c0 wow64cpu.dll!TurboDispatchJumpAddressEnd+0xf5 wow64.dll!Wow64SystemServiceEx+0x1ce wow64.dll!Wow64LdrpInitialize+0x42b ntdll.dll!RtlUniform+0x6e6 ntdll.dll!RtlCreateTagHeap+0xa7 ntdll.dll!LdrInitializeThunk+0xe ntdll.dll!NtWaitForMultipleObjects+0x15 kernel32.dll!WaitForMultipleObjectsEx+0x8e flux.exe+0x3921 ntdll.dll!RtlDeleteBoundaryDescriptor+0x1b ntdll.dll!RtlMultiByteToUnicodeN+0x11a kernel32.dll!RegSetValueExA+0x11f flux.exe+0x2841 flux.exe+0x561e8 kernel32.dll!BaseThreadInitThunk+0x12 ntdll.dll!RtlInitializeExceptionChain+0x63 ntdll.dll!RtlInitializeExceptionChain+0x36
More annoying though is the fact that it causes frame skips and audio skipping when I'm using the BSNES emulator. The only remedy is to uninstall it.
When we recompiled for 64-bit/universal (from 32-bit before), f.lux's RAM usage went from 6MB to 29MB (but Apple requested that we change it, so we did.) You could probably set f.lux to run in 32-bit mode and have the old footprint.
CoreLocation is an important feature for us, and we have to include a map and a Javascript host to access Google's geolocation service at all. There is no more reliable way than Webkit.
We've considered breaking into a daemon and a GUI, which would also allow us to make a preference pane, but it's a lot of work for not much benefit.
Using otool -L /Applications/Flux.app/Contents/MacOS/Flux you can see an impressive number of frameworks included. I guess inclusion of the webkit framework is the biggest culprit. Why all this is needed to simply dim the light on my screen is beyond me.
That said, Flux is perfect functionality wise and very useful.