Closed Bug 360636 Opened 18 years ago Closed 17 years ago

[reflow branch] ASSERTION: no common ancestor at all???: 'parent', file nsLayoutUtils.cpp, line 345

Categories

(Core :: Layout, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: MatsPalmgren_bugz, Unassigned)

References

()

Details

(Keywords: assertion, regression, testcase, Whiteboard: [dbaron-1.9:RsCr])

Attachments

(4 files)

###!!! ASSERTION: no common ancestor at all???: 'parent', file nsLayoutUtils.cpp, line 345 STEPS TO REPRODUCE 1. load the attached testcase 2. click the Reload button The assertion occurs in a Firefox debug build from REFLOW_20061031_BRANCH a few hours old. The assertion does not occur in a Firefox trunk build. (I searched for bugs that has been fixed on trunk since 20061031 but couldn't find anything). Note: the testcase uses a remote stylesheet, the assertion does not occur for me if I embed it inline using <style>.
Attached file Testcase #1 (deleted) —
FWIW, the testcase was reduced from the Minefield start page.
This seems to be worksforme....
Attached file Stack (deleted) —
Flags: blocking1.9?
Attached patch fix? (deleted) — Splinter Review
See if this fixes it (I don't have a reflow branch build yet)
(In reply to comment #5) > See if this fixes it (I don't have a reflow branch build yet) It does not fix it (same stack as before). The bug also occurs on trunk now after the reflow branch landed (same stack).
Version: Other Branch → Trunk
FWIW, I've noticed that reloading a page with generated content triggers the assertion... try reloading for example: http://meyerweb.com/eric/css/tests/css2/sec12-04-01.htm http://meyerweb.com/eric/css/tests/css2/sec12-05a.htm http://meyerweb.com/eric/css/tests/css2/sec12-05b.htm
The last time I bothered to debug this (my debugging setup is a bit screwey after I made the mistake of installing VC8SP1) one of the content nodes was a text node that didn't appear to have a parent, which I thought was odd.
Flags: blocking1.9? → blocking1.9+
Is this still an issue? I don't get this assertion with a recent trunk debug build.
Keywords: qawanted
I still don't see the assertions in my debug build. Mats, can we resolve this bug to WORKSFORME?
I have seen this assertion recently, I don't have simple STR for it though...
I don't know if it's the same one but I get one every time I switch to the CSS Style Rules viewer in DOM Inspector.
I can't seem to reproduce this on winxp/linux minefield from today, but can get a very similar stack in bug 373946. Works for me or Dupe?
Attached file stack (deleted) —
Stack using Neil's steps in comment 13. Note iframe related calls similar though not identical to bug 373946. I'll test roc's patch in attachment 247769 [details] [diff] [review] on both bugs next.
Oops, missed that the patch didn't work (and doesn't apply). If you need anything else, please re-add qawanted.
Keywords: qawanted
Is this still present? Are there current steps to reproduce?
Whiteboard: [dbaron-1.9:RsCr]
Testcase does not assert on Mac. Matthew G, does it assert for you?
I'm can't reproduce this assert with a current trunk build on Linux using the testcase, the steps in comment #7, or the using DOMi/CSS view suggested in comment #13.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: