Crashing Issues with OW 4.1b1

[Brian Covey]

Bo-
We're very interested in tracking down and fixing any memory leaks or 
problems you may have. We've never seen this, but we'd love to track it 
down and fix it!  The next time this happens, it would be quite helpful 
if you could send us the output of a "sample" command, so the lead 
developer can try to determine what OmniWeb is doing.

To do this, look up the process id for the OmniWeb process (using "top" 
or "ps" or whatever other command-line tool you prefer), then run sample 
for fifteen seconds using a command of the form "sample [pid] 15", e.g. 
"sample 12345 15" (assuming OmniWeb's process id is 12345).  Sample will 
do its analysis for 15 seconds (or whatever number you plug in), then 
write a file in /tmp (it will tell you where).  You can open this file 
with "open -e /tmp/.OmniWeb*", and then drag it (using the icon in the 
TextEdit title bar) to a compose window in Mail to attach it to a 
message to me; I'll forward it on to Ken, and we'll see if we can 
determine what's up.

Sincerely,

Brian Covey
Support Engineer
Omni Group



On Wednesday, January 2, 2002, at 01:16 PM, Bo Ahlberg wrote:

> I’m getting frequent crashes (for which the crash reports don’t make it 
> far enough to get out by email) from several sites. The most prevalent 
> site for these crashes is www.macfora.com.
>
> Symptoms:  OW 4.1b1 (after something like 4 to 5 crashes a day... this 
> sequence seems related)
> 1. Initial indicator of a pending crash is a “delayed” link – this is 
> where when a link if clicked OW pauses like it has not received the 
> click event message. By moving the Mouse the event seems to get 
> recognized and the link is processed. The pause is not an actual wait 
> period, rather it is  more like a freeze in that the wait period is 
> determined by the time before mouse motion.
>
> 2. Next Link click is responded to fairly quickly, however window draw 
> is slow with an extended beach ball time.
>
> 3. With a fairly high level of consistency the next link clicked will 
> cause a crash of OW.
>
> The time frame and activity leading up to this sequence of events seems 
> to be variable enough that I cannot place any specific steps or issues 
> on it. My experience has ranged from a near instant Crash to hours of 
> connectivity without issue. I’ve had the same crash behavior from other 
> sites... However the one listed above is the most consistent.
>
> System config:
> PowerBook G3/500 512M RAM – 18G (8G Free)
> Mac OS 10.1.2
> Major Apps installed:
> Office X
> Corel Graphics Suite for X
> Netscape for X
> AIM for X
> Solscape
>
> Typical Co-Run environment for OW
> Entourage X
> iTunes
> SetiAtHome
> SetiDock (Application version)
>
> Frequent Co-Run Applications
> Word X
> Excel X
> Explorer 5.1 (Some apps don’t seem to want to listen to the Internet 
> Settings....)
>
> Bo...