"ASSERTION: nsTHashtable was not initialized properly" after adopting textarea

RESOLVED FIXED in mozilla25

Status

()

defect
--
critical
RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: jruderman, Assigned: wchen)

Tracking

(Blocks 1 bug, {assertion, crash, testcase})

Trunk
mozilla25
Points:
---
Dependency tree / graph
Bug Flags:
in-testsuite +

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [fuzzblocker])

Attachments

(3 attachments)

Reporter

Description

6 years ago
Posted file testcase
###!!! ASSERTION: nsTHashtable was not initialized properly.: 'mTable.entrySize', file nsTHashtable.h, line 142

Probably a regression from bug 796061 or one of the others in the last push:
http://hg.mozilla.org/mozilla-central/pushloghtml?changeset=0d0263a58f06
Reporter

Comment 1

6 years ago
Posted file crash stack
Assignee

Updated

6 years ago
Assignee: nobody → wchen
Reporter

Updated

6 years ago
Whiteboard: [fuzzblocker]
Comment on attachment 781287 [details] [diff] [review]
Ensure nsBindingManager hashtable is initialized before use.

We definitely need this (and it's correct), but I was wondering aloud to wchen on IRC if we should be moving the adopted element from the bound content set of its old binding manager to the bound content set of its new binding manager on adoption.

We don't need to answer that question before landing this patch, though.
Attachment #781287 - Flags: review?(mrbkap) → review+
Assignee

Comment 4

6 years ago
https://hg.mozilla.org/integration/mozilla-inbound/rev/299df147d0e0
Flags: in-testsuite+
OS: Mac OS X → All
Hardware: x86_64 → All
https://hg.mozilla.org/mozilla-central/rev/299df147d0e0
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla25
You need to log in before you can comment on or make changes to this bug.