Leaks like a sieve

[GoogleCodeExporter]

I've proven that the leaks are due to webkit, but unfortunately it still leaks.

Linking against TOT webkit produces less leaks (to the point where it is 
acceptable imo), so there's 
basically 2 options: wait for a safari revision or replace LiveScraper with a 
non-Safari based 
implementation.

Given the difficulty of getting past the MSN passport login with a traditional 
scraper, I'm inclined to 
just wait for the update.  Another alternative would be to bundle TOT webkit, 
but that's about 
15mb, which is probably a bit much.

Original issue reported on code.google.com by james.al...@gmail.com on 11 Dec 2006 at 8:27

[GoogleCodeExporter]

I'd gladly take a bigger download until the Safari revision. I suspect most 
Xbox Live users, being broadband-
enabled, would do so as well.

Original comment by rdo...@gmail.com on 12 Feb 2007 at 11:33

[GoogleCodeExporter]

A large file is definatly fine by me if you so wish.

Original comment by remune...@googlemail.com on 13 Feb 2007 at 4:39

[GoogleCodeExporter]

Agreed, a larger download would be acceptible.

Original comment by prosenbl@gmail.com on 13 Feb 2007 at 9:55

[GoogleCodeExporter]

I agree — given it's something that you'd want to leave running for the 
Growl alerts, downloading a larger file 
once is preferable to having to restart the app all the time in order to clear 
the leak.

Original comment by wotnosp...@gmail.com on 22 Feb 2007 at 9:53

[GoogleCodeExporter]

The leaks are pretty severe and as a program that is made to be left on all the 
time
it is alittle bit of a downer, if there is a way to reduce/eliminate the leaks 
it
would really be awesome. I know its freeware so I'm not complaining just trying 
to
say a whats up, its a quality product otherwise which does everything i really 
need
of it crash free and with out errors (achievements would be cool as mentioned 
but not
real important)

thanks and I will continue to keep and eye on this page

Original comment by Matthe...@gmail.com on 9 Mar 2007 at 9:06

[GoogleCodeExporter]

Alright, if you want to run MacLive linked against a newer version of WebKit, 
here's what you gotta do:

1. Grab a nightly from webkit.org.  Hopefully it's reasonably stable.
2. Put WebKit.app from the nightly and MacLive.app into a directory next to 
each other

$ mkdir /tmp/maclive_test
$ cd /tmp/maclive_test
$ cp -r /path/to/WebKit.app /path/to/MacLive.app ./

3. Set your DYLD_FRAMEWORK_PATH to point to webkit's frameworks

$ export DYLD_FRAMEWORK_PATH=./WebKit.app/Contents/Resources/

4. Start up MacLive:
./MacLive.app/Contents/MacOS/MacLive

Now MacLive will be using the new WebKit framework that came with the WebKit 
nightly app you downloaded.

There may be an easier way to set this up, but this is how I did it and it 
works for me.  Obviously MacLive is 
may be hampered by any bugs that exist in the nightly you chose, so if it 
doesn't work or is unreliable try 
another nightly and maybe you'll have better luck.

Redistributing a snapshot of the webkit framework with MacLive isn't going to 
happen (primarily because 
google code only gives me so much space and I don't want to run out of it and 
secondarily because I don't 
want to sort through the nightlies trying to find out which one is going to 
work without eating people's dogs), 
so my official recommendation is to just hold tight until Apple releases an 
update to WebKit through Software 
Update.  

Original comment by james.al...@gmail.com on 10 Mar 2007 at 12:11

[GoogleCodeExporter]

thanks appreciate it

Original comment by Matthe...@gmail.com on 11 Mar 2007 at 9:42

[GoogleCodeExporter]

The Safari 3 beta installs a new webkit framework system wide that does not 
leak.  As a consequence, MacLive 
will no longer leak memory when the Safari 3 beta (or the final whenever that's 
released) is installed.

Original comment by james.al...@gmail.com on 11 Jun 2007 at 7:23

• Changed state: wontfix