Re: Hanging NSTextView with a paste

FROM : Mark Munz
DATE : Fri Feb 08 18:53:00 2008

Based on the customer report I received, it does seem to be
reproducible, although I am not sure how consistent it is. I am
attempting to collect additional information about the configuration
and text being pasted in. Knowing that it is likely a font issue may
help me get more information from the customer -- which will allow me
to actually file a (more useful) bug with Apple.

But it sounds like it is not related to the
setAllowsNonContiguousLayout: option -- which is good to know.

Mark Munz

On 2/8/08, Douglas Davidson <<email_removed>> wrote:
>
> On Feb 8, 2008, at 7:29 AM, Mark Munz wrote:
>
> > I received a report from a customer today that my app hangs when they
> > paste text into a NSTextView (under 10.5.1). The customer was kind
> > enough to include the hang report. It does appear that this goes deep
> > in the bowels of the text view, although it does touch my code briefly
> > (readSelectionFromPasteboard:type:) -- that quickly passes it on to
> > the NSTextView readSelectionFromPasteboard:type: .
> >
> > I recently started setting [layoutManger
> > setAllowsNonContiguousLayout:YES]; under Leopard. Are the two perhaps
> > related? Or does this sound like a different bug?
> >
> > I'm trying to understand what I can do to help reproduce this bug on
> > my end so I can log a bug with Apple (since I know the first response
> > will be to get more info).
> >
> > The user has sent in the hang reports to Apple, which may contain more
> > info -- but I don't know how those are processed or what priority they
> > may be given compared to developer generated bugs.
> >
> > Any help or insight one can give is appreciated.
> >
> > I've included the sampling that was generated:
>
> At first glance this looks like a hang somewhere in the depths of the
> font loading machinery, and nothing to do with either you or Cocoa.
> Can the customer reproduce it?  If so, you might need detailed
> information about the configuration of the customer's machine, perhaps
> the specific fonts installed, to be able to reproduce it yourself.  It
> may not be reproducible at all.  The customer's bug report will be
> attended to; the main difficulty is with reproducibility.  The
> advantage of developer bug reports is that they often contain more
> relevant details, and that we can (for example) ask developers to do
> things like capture backtraces in gdb, but if you can't reproduce it
> yourself then that's not possible.
>
> Douglas Davidson
>
>



--
Mark Munz
unmarked software
http://www.unmarked.com/