News readers & SL
J.J. O'Shea
Snow Leopard's featureset? In particular, of Grand Central Dispatch and
64-bit memory addressing? Hogwasher, for example, has a bad habit of hogging
RAM... and then running out of memory and crashing. (Yes, I just had it do
exactly that. Grrrrr....) Asar seems... unlikely... to care about fixing it
at this stage; there doesn't seem to have been any activity on a new version
of the Hog since 2007 at the latest, possibly since 2006. Anyone know about
the state of MT-NW? Or Unison, assuming that any new version of Unison has
worthwhile filters? Or any other Mac NNTP client? A new version of the Hog
would be ideal, but I've about given up on that.
--
email to oshea dot j dot j at gmail dot com.
Tim Murray
> A new version of the Hog would be ideal, but I've about given up
> on that.
Keep pestering him. I've had a couple of e-mails and he swears he's working
on a new version; he even asked for my ideas (one was thread tracking, where
you identify threads of interest to keep them alive).
Jolly Roger
J.J. O'Shea <try.n...@but.see.sig> wrote:
> Anyone know if any Mac newsreaders are being re-written to take advantage of
> Snow Leopard's featureset? In particular, of Grand Central Dispatch and
> 64-bit memory addressing? Hogwasher, for example, has a bad habit of hogging
> RAM... and then running out of memory and crashing.
64-bit addressing won't fix memory leaks. Ad I doubt Grand Central
Dispatch would help performance of a news reader very much either, if at
all.
--
Send responses to the relevant news group rather than email to me.
E-mail sent to this address may be devoured by my very hungry SPAM
filter. Due to Google's refusal to prevent spammers from posting
messages through their servers, I often ignore posts from Google
Groups. Use a real news client if you want me to see your posts.
JR
Erik Richard Sørensen
I completely agree with you! The 'Hog' is still the best stand-alone
newsreader for the Mac... - Maybe we have to push him just as hard as we
have been pushing the TypeStyler developer.:-)
Cheers, Erik Richard
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Erik Richard Sørensen, Member of ADC, <mac-m...@Mstofanet.dk>
NisusWriter - The Future In Multilingual Text Processing - www.nisus.com
OpenOffice.org - The Modern Productivity Solution - www.openoffice.org
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Király
> Anyone know if any Mac newsreaders are being re-written to take advantage of
> Snow Leopard's featureset?
I highly doubt it. Software to interface with punchcard readers is
likely not in active development for Snow Leopard either.
--
K.
Posted with tin.
J.J. O'Shea
(in article <jollyroger-53594...@news.individual.net>):
> In article <hg8r9...@news7.newsguy.com>,
> J.J. O'Shea <try.n...@but.see.sig> wrote:
>
>> Anyone know if any Mac newsreaders are being re-written to take advantage
>> of
>> Snow Leopard's featureset? In particular, of Grand Central Dispatch and
>> 64-bit memory addressing? Hogwasher, for example, has a bad habit of
>> hogging
>> RAM... and then running out of memory and crashing.
>
> 64-bit addressing won't fix memory leaks. Ad I doubt Grand Central
> Dispatch would help performance of a news reader very much either, if at
> all.
>
>
it's not so much a memory leak as when you have multiple threads open it
_will_ grab all the RAM available. Once the threads close it always releases
the RAM... but if it thinks that it needs more RAM than is available, and VM
doesn't react quickly enough, it crashes. I've had the Hog grab 3 GB out of 4
GB of physical RAM and another 3 GB of VM and still want more. GCD might be
useful if several major threads were running at once, such as (for example)
updating headers for high-traffic news groups such as r.a.sf.w and c.s.m.s at
the same time. Doing that with the current version brings out the Spinning
Pizza of Death for a minute or two, and you can't do anything with the Hog
while the SPoD is up. Worse, that's when the Hog is usually grabbing a lot of
RAM, so it slows everything else down and you can't do much with other apps
either. As soon as the update is over, the SPoD goes away and the RAM usage
drops down from 3 GB physical RAM and 3.5 GB VM to 51 MB and 41 MB,
respectively. And yes, I got those RAM figures by looking at Activity Monitor
the last time the Hog went into SPoD mode and comparing it to what showed up
immediately after the SPoD went away. (The Hog also had 105% CPU usage
compared with 2.1%...) If the SPoD hangs around for more than a few minutes
the Hog crashes.
There is definitely room for improvement.
David Blanchard
And I suppose that means no software to interface with my 7-track and 9track
tape drives, either. Time to move on...
-db-
Posted with trn. ;-)
--
+-----------------------------------------------------------------+
| David O. Blanchard d...@npgcable.com Flagstaff, Arizona |
+-----------------------------------------------------------------+
ZnU
J.J. O'Shea <try.n...@but.see.sig> wrote:
> On Tue, 15 Dec 2009 17:00:38 -0500, Jolly Roger wrote (in article
> <jollyroger-53594...@news.individual.net>):
>
> > In article <hg8r9...@news7.newsguy.com>,
> > J.J. O'Shea <try.n...@but.see.sig> wrote:
> >
> >> Anyone know if any Mac newsreaders are being re-written to take
> >> advantage of Snow Leopard's featureset? In particular, of Grand
> >> Central Dispatch and 64-bit memory addressing? Hogwasher, for
> >> example, has a bad habit of hogging RAM... and then running out of
> >> memory and crashing.
> >
> > 64-bit addressing won't fix memory leaks. Ad I doubt Grand Central
> > Dispatch would help performance of a news reader very much either,
> > if at all.
> >
> >
>
> it's not so much a memory leak as when you have multiple threads open
> it _will_ grab all the RAM available. Once the threads close it
> always releases the RAM... but if it thinks that it needs more RAM
> than is available, and VM doesn't react quickly enough, it crashes.
> I've had the Hog grab 3 GB out of 4 GB of physical RAM and another 3
> GB of VM and still want more.
The solution there is to fix whatever is causing it to try to grab vast
qualities of RAM for tasks that shouldn't require it, not allow it to
grab even more vast qualities of RAM. (That's all we need: 64-bit apps
with horrible memory leaks trying to grab a few million terabytes of
RAM.)
> GCD might be useful if several major threads were running at once,
> such as (for example) updating headers for high-traffic news groups
> such as r.a.sf.w and c.s.m.s at the same time. Doing that with the
> current version brings out the Spinning Pizza of Death for a minute
> or two, and you can't do anything with the Hog while the SPoD is up.
This sort of UI blocking is fixable with plain old regular threading,
though GCD might be less work for the developer.
> Worse, that's when the Hog is usually grabbing a lot of RAM, so it
> slows everything else down and you can't do much with other apps
> either. As soon as the update is over, the SPoD goes away and the RAM
> usage drops down from 3 GB physical RAM and 3.5 GB VM to 51 MB and 41
> MB, respectively. And yes, I got those RAM figures by looking at
> Activity Monitor the last time the Hog went into SPoD mode and
> comparing it to what showed up immediately after the SPoD went away.
> (The Hog also had 105% CPU usage compared with 2.1%...) If the SPoD
> hangs around for more than a few minutes the Hog crashes.
>
> There is definitely room for improvement.
--
"The game of professional investment is intolerably boring and over-exacting to
anyone who is entirely exempt from the gambling instinct; whilst he who has it
must pay to this propensity the appropriate toll." -- John Maynard Keynes
Jolly Roger
My goodness. MT-NewsWatcher uses in the vicinity of 20-30 *megabytes* on
my machine when it checks for new messages.
Tim Murray
> it's not so much a memory leak as when you have multiple threads open it
> _will_ grab all the RAM available. Once the threads close it always releases
> the RAM... but if it thinks that it needs more RAM than is available, and VM
> doesn't react quickly enough, it crashes. I've had the Hog grab 3 GB out of 4
> GB of physical RAM and another 3 GB of VM and still want more. GCD might be
> useful if several major threads were running at once, such as (for example)
> updating headers for high-traffic news groups such as r.a.sf.w and c.s.m.s at
> the same time. Doing that with the current version brings out the Spinning
> Pizza of Death for a minute or two, and you can't do anything with the Hog
> while the SPoD is up. Worse, that's when the Hog is usually grabbing a lot of
> RAM, so it slows everything else down and you can't do much with other apps
> either. As soon as the update is over, the SPoD goes away and the RAM usage
> drops down from 3 GB physical RAM and 3.5 GB VM to 51 MB and 41 MB,
> respectively. And yes, I got those RAM figures by looking at Activity Monitor
> the last time the Hog went into SPoD mode and comparing it to what showed up
> immediately after the SPoD went away. (The Hog also had 105% CPU usage
> compared with 2.1%...) If the SPoD hangs around for more than a few minutes
> the Hog crashes.
>
I've been using HW for years and don't see that kind of behavior unless I'm
updating headers and manage to pull in some tens of thousands. Real memory
doesn't go over 36 (but I never have more than two threads open) and virtual
over 268; CPU peaks at 12%. I'm using a PowerBook G4 on 10.4.11.