We also get these exceptions on lines 123, 125 and 127 of preferences.js
Googling this error message implies that it is normally caused by the use of "E4X".
It isn't at first obvious how that relates to places that are throwing these exceptions. However we use E4X in the functions ParseXmlRulesets and PraseOneRuleset, and the errors are being raised in places that refer to objects built from XML input in those functions.
So it seems that ParseXmlRulesets and ParseOneRuleset will need to be rewritten using some alternative non-E4X means of parsing XML rulesets.
Another person reported seeing this, CC'ing them here. What we need is a patch that replaces all the E4X in ParseXmlRulesets and ParseOneRuleset with either cruder DOM inspection, or JXON.
Commit fc91c08f4a4260a123d3563fd0bd9765a7498d3d is meant to address this (via the "cruder DOM inspection" approach, getting rid of all the E4X syntax).