[Webkit-unassigned] [Bug 12949] WebKit crash in DOM::NodeImpl::setChanged(bool)

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Mar 2 17:41:58 PST 2007


------- Comment #3 from ddkilzer at webkit.org  2007-03-02 17:41 PDT -------
(In reply to comment #2)
> I would love to be able to get a reproducable scenario, it took us months to
> finally have somebody properly give us a crash report and then they didn't know
> exactly what they were doing.

If any of your users sent a crash report to Apple, the Safari engineers may be
able to review similar stacks and provide a count of how many times it was
reported, but probably won't have much more information than that.

> I don't know the internals of the WebKit well, but reading the call stack, it
> seems that the user might have been trying to copy / paste text or something
> along those lines? Am I right with this guess?

My analysis of the stack trace was that the user clicked on a URL with a hash
on it (foo.html#bar), but I'm not sure what the last two method calls do.  (I'm
not as familiar with the "older" internal WebKit APIs from the Tiger era.)

Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the webkit-unassigned mailing list