Bug 144101 – Look up will deepend every time.

• Component: New Bugs
• Status: RESOLVED FIXED

[Jim Oase]

Created attachment 251445 [details]
Screen shot of Lookup Failing

See attached screen shot.

The last couple of releases of the nightly build will crash when attempting to lookup the definition of a word.

[Tim Horton]

The crash is in the Lookup process, not WebKit; you should file this at bugreport.apple.com, instead of here.

[Jim Oase]

(In reply to comment #1)
> The crash is in the Lookup process, not WebKit; you should file this at
> bugreport.apple.com, instead of here.

Works correctly with Safari and other applications, not with WebKit.

[Tim Horton]

Hmm, indeed, it seems to reproduce in nightlies. Interesting! Un-resolving for now.

[Tim Horton]

But not in ToT builds?!

[Brent Fulgham]

(In reply to comment #0)
> Created attachment 251445 [details]
> Screen shot of Lookup Failing
> 
> See attached screen shot.
> 
> The last couple of releases of the nightly build will crash when attempting
> to lookup the definition of a word.

Could you paste the full text of that crash report dialog here so we can look at it?

[Beth Dakin]

I wonder if this could have something to do with the fact that Nightlies are not yet building with the 10.3 SDK.

[Tim Horton]

(In reply to comment #5)
> Could you paste the full text of that crash report dialog here so we can
> look at it?

No need for this, the bug is easily reproducible.

This is a regression in OS 10.10.3, not in WebKit; please file a bug at bugreport.apple.com, instead of here.

[Jim Oase]

(In reply to comment #7)
> (In reply to comment #5)
> > Could you paste the full text of that crash report dialog here so we can
> > look at it?
> 
> No need for this, the bug is easily reproducible.
> 
> This is a regression in OS 10.10.3, not in WebKit; please file a bug at
> bugreport.apple.com, instead of here.

So far the only application with this problem is WebKit.  Is this one of those "Look everyone except Johnny is out of step" deals?

[Jim Oase]

Created attachment 252053 [details]
Screen shot of failure.. next will be dialog

[Jim Oase]

Created attachment 252054 [details]
Dialog of lookup crash

[Alexey Proskuryakov]

WebKit nightlies are indeed unusual, because they use Safari that is installed on your system. This is an integral part of how nighlties work, so as Tim said, this is a bug in OS X 10.10.3 that needs to be reported to Apple.

Thank you for following up!

[Jim Oase]

(In reply to comment #11)
> WebKit nightlies are indeed unusual, because they use Safari that is
> installed on your system. This is an integral part of how nighlties work, so
> as Tim said, this is a bug in OS X 10.10.3 that needs to be reported to
> Apple.
> 
> Thank you for following up!

In another life I had programmers tell me their code was good so its got to be something else causing the problem.  My approach was to ask for a walk through of the code with a couple more people sitting in.

An amazing number of times, during the presentation, the programmer would stop, make an amazement statement and the problem was found.


So the premise is that when Safari and all other applications do the lookup routines they accesses OS X is a different way than WebKit even though Safari and WebKit use the same routines?   

What is the problem that causes OSX to recognize and treat WebKit different?  

Does OSX know it's WebKit calling via Safari routines?

What changed between the build that worked and the first one that didn't work?  Did OSX get an upgrade?  I will look back at builds and find when the change occurred.  If there is such an occurrence than OSX is not the problem.

[Tim Horton]

(In reply to comment #12)

> What changed between the build that worked and the first one that didn't
> work?  Did OSX get an upgrade? 

Yes, 10.10.3.

> I will look back at builds and find when the
> change occurred.  If there is such an occurrence than OSX is not the problem.

The problem is fully understood, there's no need to investigate further, we just cannot discuss the problem here -- that discussion's place is in Apple's bug reporter.

[Alexey Proskuryakov]

*** Bug 145105 has been marked as a duplicate of this bug. ***