| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
On 25 Oct 2007, at 15:49, Gerben Wierda wrote:
In this situation I would be using lsof to monitor the open file handles as the app runs. Something like
lsof -p <pid> -n +r 5
will show you all the open files of your process, and which ones are lasting longer than they should. Alternatively, using sharks 'System Trace' may help by allowing you to see what file-handles are used by what system call, and when they should have been released. That's not as easy to decode though.
I know lsof (I think I used lsof the last time to see if it could help me
find out what was happening) I'll look into Shark.
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
| References: | |
| >Troublesome app when scaling it up, how to proceed? (From: Gerben Wierda <email@hidden>) | |
| >Re: Troublesome app when scaling it up, how to proceed? (From: David Spooner <email@hidden>) | |
| >Re: Troublesome app when scaling it up, how to proceed? (From: "Gerben Wierda" <email@hidden>) | |
| >Re: Troublesome app when scaling it up, how to proceed? (From: Thomas Engelmeier <email@hidden>) | |
| >Re: Troublesome app when scaling it up, how to proceed? (From: "Gerben Wierda" <email@hidden>) | |
| >Re: Troublesome app when scaling it up, how to proceed? (From: Paul Sargent <email@hidden>) | |
| >Re: Troublesome app when scaling it up, how to proceed? (From: "Gerben Wierda" <email@hidden>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.