Closed
Bug 503562
Opened 15 years ago
Closed 15 years ago
KB Article:Crash signature - nsStyleSet::FileRules(int (*)(nsIStyleRuleProcessor*, void*), RuleProcessorData*)
Categories
(support.mozilla.org :: Knowledge Base Articles, task)
support.mozilla.org
Knowledge Base Articles
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: cilias, Assigned: bbayles)
References
()
Details
I'm not sure of the cause or solution, so the article name is up in the air; but @ nsStyleSet::FileRules(int (*)(nsIStyleRuleProcessor*, void*), RuleProcessorData*) is a top crash. The crash bug is bug 492675.
Current guesses are it's related to the MyWebSearch Toolbar which is spyware and also called ASK toolbar or Zone alarm toolbar, see also bug 466024. But I asked for more QA so we'll be able to confirm that.
Reporter | ||
Updated•15 years ago
|
Severity: normal → major
Reporter | ||
Comment 2•15 years ago
|
||
Notes for article: - the issue is under investigation - most likely caused by ask toolbar or mywebsearch
Summary: User-doc for crashsig: @ nsStyleSet::FileRules(int (*)(nsIStyleRuleProcessor*, void*), RuleProcessorData*) → KB Article:Crash signature - @ nsStyleSet::FileRules(int (*)(nsIStyleRuleProcessor*, void*), RuleProcessorData*)
Draft is up, ready for review. I left all of the symbol craziness out of the URL for this one, add back what won't cause problems please.
Status: NEW → RESOLVED
Closed: 15 years ago
QA Contact: kb-articles → bbayles
Resolution: --- → FIXED
Reporter | ||
Comment 4•15 years ago
|
||
Reviewed and moved KB at: Wed 19 of Aug, 2009 23:56 EST
Assignee: nobody → bbayles
Status: RESOLVED → VERIFIED
QA Contact: bbayles → kb-articles
Reporter | ||
Updated•15 years ago
|
Summary: KB Article:Crash signature - @ nsStyleSet::FileRules(int (*)(nsIStyleRuleProcessor*, void*), RuleProcessorData*) → KB Article:Crash signature - nsStyleSet::FileRules(int (*)(nsIStyleRuleProcessor*, void*), RuleProcessorData*)
special characters break tiki. https://support.mozilla.com/en-US/kb/Crash+signature+-+nsStyleSet+FileRules
You need to log in
before you can comment on or make changes to this bug.
Description
•