Pageout crashes with Entourage 2004

[Guest]

For the past 8 months, I've been noticing that Entourage is the primary
culprit in crashes and spinning beachballs. I send in my reports faithfully.
Some say it is related to OSX updates. However, it is almost always when
clicking on HTML emails that Entourage chokes, cycles and then quits.
Sometimes it even freezes up my finder, as today, when I started seeing
Pageouts skyrocket when clicking on one email and having it cycle the finder
forever.
I have done deep system cleanings, rebuilt the E databases. They always
report stable and no problems.

Today, I am starting to think about switching email programs, which I
haven't considered in a long time. Admittedly, I may be running a lot of
programs under OSX 10.4.10 but I have 3.5 gigs of ram and the free memory is
till over 40% at peak use. What happened was Ent started hogging all
available ram.

I was hoping the 2008 release might fix this problem, but I am no longer
hopeful and do not want to buy an update to find the same problems.

Jeff
~~~~~~~~~~~~
Jefferis Peterson, Pres.
Web Design and Marketing
http://www.PetersonSales.com

 

[jtimleck]

I agree - this is frustrating - and it doesn't happen to me with html OR
attachments - just any mail. As the program opens and loads new mail from the
server if you click on ANYTHING it chokes and freezes. You then have to force
quit it and then it takes literally two or three minutes to re-open (I'm
assuming it's rebuilding its database). I've done deep cleaning too, manually
rebuilt the database etc. Now I *do* keep my profile on a separate disk than
the OS, but this shouldn't be a problem.

frustrated...

 

[Guest]

I'm obviously less tech-savvy than the two previous posters, as I have no idea what deep system cleaning is. If it's housekeeping, I don't wanna know! But my problem with Entourage is that whenever I try to delete more than say two or three e-mails in a row, I get the spinning beach ball of inertia, and everything freezes up and I have to force quit. Does Microsoft have a fix for this? I'm current with all the updates, so I don't think that's it.

 

[Diane Ross]

I'm obviously less tech-savvy than the two previous posters, as I have no idea
what deep system cleaning is. If it's housekeeping, I don't wanna know! But
my problem with Entourage is that whenever I try to delete more than say two
or three e-mails in a row, I get the spinning beach ball of inertia, and
everything freezes up and I have to force quit. Does Microsoft have a fix for
this? I'm current with all the updates, so I don't think that's it.

This is not a Microsoft problem. What version of Entourage are you using?
What version of the OS? How large is your HD and how full? How much RAM do
you have? Do you always leave your computer on, or do you restart often?

When Entourage starts spinning, open the Activity Monitor in your
Application/Utilities folder. Is Entourage red to indicate it's crashing? If
you double click on Entourage in the Activity Monitor list while it's
spinning and click on the Sample button, can you copy that log and post it
here?

 

[linda hodges]

We are having a similar problem, and I am doing as you said.
bellow is our activity monitor script. does this help?
-thanks
-lhodges

Analysis of sampling pid 185 every 10.000000 milliseconds
Call graph:
193 Thread_0f0f
193 0x20c62fc
193 0x4bf2c0
193 0x20c91dc
193 0x4bf4f0
193 0x4c3a44
193 0x4c3c2c
193 0x2538f40
193 0x50968c
193 YieldToThread
193 SwitchContexts
193 mach_msg
193 mach_msg_trap
193 mach_msg_trap
193 Thread_1003
193 _pthread_body
193 MerpUnregisterCFMFragment
193 mach_msg
193 mach_msg_trap
193 mach_msg_trap
193 Thread_1103
193 _pthread_body
193 PrivateMPEntryPoint
193 _MP_CFMTaskProc
193 0x6aa56c
193 0x6aa388
193 0x749974
193 FWaitForConnection
193 accept
193 accept
193 Thread_1203
193 _pthread_body
193 PrivateMPEntryPoint
193 _MP_CFMTaskProc
193 0x6aa934
193 0x6aa79c
193 0x749aec
193 FReceiveMessage
193 recvfrom
193 recvfrom
193 Thread_1303
193 _pthread_body
193 PrivateMPEntryPoint
193 _MP_CFMTaskProc
193 0x6aaad8
193 MPWaitOnSemaphore
193 pthread_cond_timedwait_relative_np
193 semaphore_timedwait_signal_trap
193 semaphore_timedwait_signal_trap
193 Thread_1403
193 _pthread_body
193 CooperativeThread
193 InvokeThreadEntryUPP
193 0x50a8b4
193 0x2540938
193 0x22e6f94
193 0x22e5b64
193 0x22e6338
193 0x2459a64
193 0x2459fe0
193 0x2459b28
193 0x22cb6a0
193 0x22cbbb4
193 0x22cba5c
193 0x22d1578
193 0x22cb930
193 0x22ce9c4
193 0x22ce498
193 0x22d087c
19 0x1285ca0
19 0x1285ca0
16 0x1285bf0
16 0x4a7544
8 0x4a7598
7 HGetState
4 CSMemHGetState
4 malloc_size
2 malloc_size
2 szone_size
2 szone_size
2 HGetState
1 LMSetMemErr
1 LMSetMemErr
1 LMSetMemErr
1 LMSetMemErr
8 0x4a75d4
8 HLock
8 CSMemHModifyState
5 malloc_size
3 szone_size
3 szone_size
2 malloc_size
3 CSMemHModifyState
16 0x1285c9c
16 0x1285c9c
13 0x1285c50
13 0x1285c50
9 0x1285c58
9 0x1285c58
9 0x1285c70
9 0x1285c70
8 0x1285c7c
8 0x1285c7c
8 0x13e1c40
8 0x13e1c40
6 0x1285c40
4 0x1280d48
4 0x1280d48
1 0x12833f4
1 0x12833f4
1 0x1285c40
6 0x1285c78
6 0x1285c78
5 0x128372c
5 0x128372c
5 0x1285c54
5 0x1285c54
5 0x1285dc0
5 0x1285dc0
4 0x1283730
4 0x1283730
4 0x1285d80
4 0x1285d80
4 0x1292a00
4 0x1292a00
4 0x13e1c48
4 0x13e1c48
4 0x13e1c6c
4 0x13e1c6c
4 0x13e1c70
4 0x13e1c70
3 0x1285ca4
3 0x1285ca4
3 0x1285db8
3 0x1285db8
3 0x1285f0c
3 0x4a79f0
3 0x4a7618
2 LMSetMemErr
2 GetThreadGlobals
2 GetThreadGlobals
1 HUnlock
1 CSMemHModifyState
1 malloc_size
1 malloc_size
3 0x1292a10
3 0x1292a10
2 0x128374c
2 0x128374c
2 0x1285d34
2 0x13df610
2 0x13df610
2 0x1285e1c
2 0x1285e1c
2 0x1292a08
2 0x1292a08
2 0x1292a0c
2 0x1292a0c
2 0x13e1c58
2 0x13e1c58
2 0x13e1c5c
2 0x13e1c5c
2 0x13e1c84
2 0x13e1c84
1 0x1280d04
1 0x1280d04
1 0x12834ec
1 0x12834ec
1 0x1283588
1 0x1283588
1 0x12835dc
1 0x12835dc
1 0x1285c88
1 0x1285c88
1 0x1285c8c
1 0x1285c8c
1 0x1285d8c
1 0x1285d8c
1 0x1285dc4
1 0x1285dc4
1 0x1285de0
1 0x1285de0
1 0x1285e14
1 0x1285e14
1 0x1285e18
1 0x1285e18
1 0x1285e44
1 0x1285e44
1 0x1285e50
1 0x1285e50
1 0x1285e84
1 0x1285e84
1 0x1285e98
1 0x1285e98
1 0x1292a04
1 0x1292a04
193 Thread_1503
193 _pthread_body
193 CooperativeThread
193 InvokeThreadEntryUPP
193 0x50a8b4
193 0x2540938
193 0x22bb0c4
193 0x244f9d0
193 0x244fdd0
193 0x244fa70
193 0x2453c64
193 0x2455478
193 0x245550c
193 0x2431650
193 0x24319c8
193 0x243200c
193 0x23792c4
193 0x2457d00
193 0x23794cc
193 0x23844d8
193 0x2384ba0
193 0x758000
193 NLCreateConnection
193 NLDisposeClientContext
193 NLDisposeClientContext
193 NLDisposeClientContext
193 NLNotifyThread
193 NLNotifyThread
193 NLThreadSleep
193 NLThreadSleep
193 NLThreadSleep
193 NLThreadSleep
193 0x237a798
193 0x237a598
193 0x237a70c
193 0x237a8f0
193 0x50968c
193 YieldToThread
193 SwitchContexts
193 mach_msg
193 mach_msg_trap
193 mach_msg_trap
193 Thread_1603
193 _pthread_body
193 CooperativeThread
193 InvokeThreadEntryUPP
193 0x50a8b4
193 0x2540938
193 0x237c480
193 0x237c430
193 0x4a6c60
193 0x2541204
193 0x2541154
193 0x50968c
193 YieldToThread
193 SwitchContexts
193 mach_msg
193 mach_msg_trap
193 mach_msg_trap

Total number in stack (recursive counted multiple, when >=5):
7 _pthread_body

Sort by top of stack, same collapsed (when >= 5):
mach_msg_trap 772
accept 193
recvfrom 193
semaphore_timedwait_signal_trap 193
0x1285ca0 19
0x1285c9c 16
0x1285c50 13
0x1285c58 9
0x1285c70 9
0x1285c7c 8
0x13e1c40 8
0x1285c78 6
0x128372c 5
0x1285c54 5
0x1285dc0 5
malloc_size 5
szone_size 5
Sample analysis of process 185 written to file /dev/stdout
Sampling process 185 each 10 msecs 300 times

 

[Diane Ross]

We are having a similar problem, and I am doing as you said.
bellow is our activity monitor script. does this help?

I'll pass this on to see if I can get an experienced opinion, but it seems
you have connected, but are stalling out on a message. If you install
tcpflow it will show you what message is the problem and you can delete it
via your web interface.

Here are the short and simple instructions on using tcpflow: (the directions
are longer than the process)

1. Download the Mac OS X version here (freeware).

<http://web.archive.org/web/20020610050659/http://www2.entropy.ch/download/t
cpflow-0.20.dmg.gz>

2. When you install, you will not find a tcpflow window, nor an icon on
your dock. tcpflow is designed to work in the background.

3. To run the test for email, quit all other applications that might be
connecting to the internet like your browser, ftp client.

4. Copy/paste in this command in the Terminal or use the script ²tcpflow
activate² (see below):

sudo /usr/local/bin/tcpflow -i en0 -c

5. Now try to send an email and watch the traffic in the window of the
Terminal. You should see what is happening.

6. For an example see this page:

<http://www.entourage.mvps.org/troubleshoot/tcpflow.html#example>

Script to activate tcpflow:

Download this script and place it in your User's Script folder.

<http://www.entourage.mvps.org/downloads/scripts/tcpflow activate.zip>

Place the script here:

Users --> Library --> Script folder

If you activate the Script Menu in the Finder you can easily access the
script there. To activate the Script menu, go to your Applications folder in
the Finder. Select the AppleScript folder and open AppleScript Utility. ˆ
Show Script Menu in menu bar

Select the script to automatically start the Terminal with the correct
command. Enter your password and tcpflow will be activated. Next use
Entourage to send a test message.

Using the script makes it easy to use tcpflow for subsequent testing.