http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2660 *** shadow/2660 Tue Jul 17 13:55:30 2001 --- shadow/2660.tmp.443 Tue Jul 17 13:55:30 2001 *************** *** 0 **** --- 1,35 ---- + +============================================================================+ + | SAX Major Memory Leak | + +----------------------------------------------------------------------------+ + | Bug #: 2660 Product: Xerces-C++ | + | Status: NEW Version: 1.5 | + | Resolution: Platform: PC | + | Severity: Major OS/Version: Windows NT/2K | + | Priority: Other Component: SAX/SAX2 | + +----------------------------------------------------------------------------+ + | Assigned To: [EMAIL PROTECTED] | + | Reported By: [EMAIL PROTECTED] | + | CC list: Cc: | + +----------------------------------------------------------------------------+ + | URL: | + +============================================================================+ + | DESCRIPTION | + I am using SAX 1.0 to read in a very large XML file. Without even assigning a + document handler I noticed (in Task Manager) that the memory usage for my + application goes through the roof! The application was consuming several + hundred MB of virtual space, slowing down the app dramatically, which is why I + noticed. + + I back ported to 1.4 and ran the same code (removing the calls to setDoSchema + and setValidationConstraintFatal, both of which were false) and the memory + consuption flatlined beautifully. + + SAXParser parser; + parser.setDoNamespaces( false ); // None in the document + parser.setValidationScheme( SAXParser::Val_Never ); + //parser.setDoSchema( false ); + parser.setExitOnFirstFatalError( true ); + // parser.setValidationConstraintFatal( false ); + parser.parse( dictionaryFileName ); + + This is similar to bug #2649, but more specific. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
