• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Over-released Paragraph Style - Driving Me NUTS!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Over-released Paragraph Style - Driving Me NUTS!


  • Subject: Re: Over-released Paragraph Style - Driving Me NUTS!
  • From: Seth Willits <email@hidden>
  • Date: Fri, 20 Oct 2006 13:27:40 -0700

On Oct 20, 2006, at 1:15 PM, j o a r wrote:

I've never used ObjectAlloc before, so it sounds neat. However, it's been running for the last half an hour and still hasn't gotten to the 100% repeatable crash yet on a dual 2.3 G5. This is rather painful...

ObjectAlloc is incredibly neat! It's an indispensable part of the Cocoa toolkit! There is also OmniObjectMeter from the good fellows at OmniGroup, I think it provides roughly the same functionality.


Now, ObjectAlloc does require a lot of resources - especially in the configuration I advised you to use. It's particularly important to have lots of RAM. If you start swapping, you're basically toast. Check with Activity Monitor / top to see if you're OK on that front or not.

It also helps if you can get to the problematic code as quickly as possible after launching your app. Perhaps you can tweak it a bit to avoid having it load / run other parts of your code while troubleshooting this issue? You might even want to try moving your problematic code to a small sample application.



I got it working. I have two and a half gigs of RAM, so that's not an issue. I don't know why, but the app gets to a certain spot and just sits and does nothing after a certain point unless I attach the debugger to it after launching it with ObjectAlloc.


The crash occurs while opening and initially displaying a text document, so what I did was launch it with ObjectAlloc, attach the debugger, pause and find the pointer value of the paragraph style that's getting clobbered, and then continued and opened the doucment. After a while later (and figuring out I had to call continue in gdb because of some weirdness) it finally hit the exception and I was able to find the pointer in ObjectAlloc.

The only thing is that it didn't help me at all. There are three events for the object, the alloc, the autorelease, and the free. The alloc is from the buildParagraphStyle method, the autorelease is from the same, and the release is from the autorelease pool. Despite checking the box to manage retain and release calls, they were not, so I have no more information than when I started. Am I missing something?



--
Seth Willits



_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Over-released Paragraph Style - Driving Me NUTS!
      • From: j o a r <email@hidden>
References: 
 >Over-released Paragraph Style - Driving Me NUTS! (From: Seth Willits <email@hidden>)
 >Re: Over-released Paragraph Style - Driving Me NUTS! (From: j o a r <email@hidden>)
 >Re: Over-released Paragraph Style - Driving Me NUTS! (From: Seth Willits <email@hidden>)
 >Re: Over-released Paragraph Style - Driving Me NUTS! (From: j o a r <email@hidden>)

  • Prev by Date: Re: unwanted cell copy being interposed during click in outline
  • Next by Date: Re: Over-released Paragraph Style - Driving Me NUTS!
  • Previous by thread: Re: Over-released Paragraph Style - Driving Me NUTS!
  • Next by thread: Re: Over-released Paragraph Style - Driving Me NUTS!
  • Index(es):
    • Date
    • Thread