• 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: NSTableView/NSOutlineView variable row height code has detected re-entry.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSTableView/NSOutlineView variable row height code has detected re-entry.


  • Subject: Re: NSTableView/NSOutlineView variable row height code has detected re-entry.
  • From: Clark Cox <email@hidden>
  • Date: Wed, 8 Sep 2010 11:42:55 -0700

On Wed, Sep 8, 2010 at 11:11 AM, Keith Blount <email@hidden> wrote:
> Hello,
>
> I have an NSOutlineView with variable row heights, as determined in
> my -outlineView:heightOfRowByItem: delegate method. This has always seemed to
> work fine, and the code of this delegate method hasn't changed much in the past
> three years, but I have had a user report a case whereby his outline view
> appeared completely blank and this message appeared on the console:
>
> NSTableView/NSOutlineView variable row height code has detected re-entry.
> Avoiding a crash....
>
> After restarting the program, he hasn't seen the problem since, so I haven't
> been able to reproduce it. But I did see it myself during testing once last year
> and then, too, I wasn't able to reproduce it a second time. I've Googled for
> this message and can only find a couple of other posts referencing it, with no
> solution. One problem is that I don't know exactly what the message means by
> "re-entry", so I'm not sure whether the problem is with the variable row height
> code itself (which seems fine), or because the row height code is somehow
> getting called twice during layout, or something else entirely. I've gone
> through the code but can find no obvious culprit (which is probably not
> surprising given the rarity of the error).
>
> Has anybody else seen this error, or does anybody know what it means?

Essentially, it means just what it says. Something has called into the
code responsible for recording the row heights for a table view, while
that same code was already running.

Some potential causes:
- Recursion: Your -tableView:heightOfRow: delegate method is doing
something that is calling -reloadData, or
-noteHeightOfRowsWithIndexesChanged: (or something else that causes
recalculation of row heights)
- Concurrency: You're accessing the table, its delegate, or its data
source from multiple threads.

--
Clark S. Cox III
email@hidden
_______________________________________________

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:

This email sent to email@hidden

  • Follow-Ups:
    • Re: NSTableView/NSOutlineView variable row height code has detected re-entry.
      • From: Keith Blount <email@hidden>
References: 
 >NSTableView/NSOutlineView variable row height code has detected re-entry. (From: Keith Blount <email@hidden>)

  • Prev by Date: NSTableView/NSOutlineView variable row height code has detected re-entry.
  • Next by Date: Re: NSNumber compare: Giving Unexpected Results
  • Previous by thread: NSTableView/NSOutlineView variable row height code has detected re-entry.
  • Next by thread: Re: NSTableView/NSOutlineView variable row height code has detected re-entry.
  • Index(es):
    • Date
    • Thread