Path: utzoo!censor!geac!jtsv16!uunet!jarthur!usc!zaphod.mps.ohio-state.edu!math.lsa.umich.edu!sharkey!msuinfo!netnews.upenn.edu!pohl.cis.upenn.edu!grobbins
From: grobbins@pohl.cis.upenn.edu (Grobbins)
Newsgroups: comp.sys.mac.system
Subject: Re: 6.0.5 and System Heap questions...
Summary: crash city for me, plus Wingz is crippled
Message-ID: <24462@netnews.upenn.edu>
Date: 3 May 90 06:01:35 GMT
References: <1990May3.032903.14589@athena.mit.edu> <40701@apple.Apple.COM>
Sender: news@netnews.upenn.edu
Reply-To: grobbins@eniac.seas.upenn.edu
Distribution: usa
Organization: U. of Pennsylvania
Lines: 27

In article <40701@apple.Apple.COM> chuq@Apple.COM writes:
>I've been running 6.0.5 myself and beating the h*ck out of it for a while.
>I've seen absolutely no problems that I didn't have with 6.0.4 

I've had many, many crashes when app-hopping under 6.0.5 which weren't
repeatable enough to file a bug report, but which did not occur under
6.0.4.  Applications also quit spontaneously, and other strange
happenings occur.  I'm now in the habit of saving before switching out
of an application under 6.0.5.

Wingz 1.1 won't launch a second time under 6.0.5; according to an earlier
post, the programmer knows the bug.  (That hurts; I'm doing large neural
net simulations in Wingz, and have to leave it frequently.  Restarting
the Mac to restart the program is annoying.)

Unless you need one of the 6.0.5 bug fixes, I'd say stick with 6.0.4.  
(Yeah, Chuq, this is too general to be useful, but it is my experience.
You couldn't pay me to track down system software bugs again.)

The system seems more sensitive to full memory; I've had to increase
the heap substantially, which I had never done before.  And in the
process of typing this, I hit another problem, a hang when choosing
About the Finder, which has happened before under 6.0.5.

Living on the edge,

Grobbins.    grobbins@eniac.seas.upenn.edu