Summary: | Correction to earlier AttributesImpl bug-fix | ||
---|---|---|---|
Product: | XmlCommons - Now in JIRA | Reporter: | Glenn Marcy <gmarcy> |
Component: | SAX | Assignee: | Commons Developers Mailing List <commons-dev> |
Status: | NEW --- | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 1.x | ||
Target Milestone: | --- | ||
Hardware: | Other | ||
OS: | other |
Description
Glenn Marcy
2001-10-12 13:17:35 UTC
Do we have a test program that shows the effects of this bug on another Apache product yet? I am not sure how to create one exactly. The reason for the initial report is not know to me, except that from inspection I can see that the original code did not clear the "slots" following the new last entry after a call to remove an attribute. This would simply leave references to String objects that would not be collectable during gc(), but would otherwise seem to be benign (they are immutable after all...) My changes were to simply take the "spirit" of the original fix and change the code to clear the String references so that the entries in the array were always null beyond the last in-use entry. Perhaps we should ask garyp or dims if they have more information to offer. |