PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3565

*** shadow/3565 Wed Sep 12 06:59:45 2001
--- shadow/3565.tmp.16956       Wed Sep 12 06:59:45 2001
***************
*** 0 ****
--- 1,24 ----
+ +============================================================================+
+ | stream leaked in ReaderMgr                                                 |
+ +----------------------------------------------------------------------------+
+ |        Bug #: 3565                        Product: Xerces-C++              |
+ |       Status: NEW                         Version: 1.5.1                   |
+ |   Resolution:                            Platform: All                     |
+ |     Severity: Normal                   OS/Version: Other                   |
+ |     Priority: Other                     Component: Miscellaneous           |
+ +----------------------------------------------------------------------------+
+ |  Assigned To: [EMAIL PROTECTED]                                  |
+ |  Reported By: [EMAIL PROTECTED]                                          |
+ |      CC list: Cc:                                                          |
+ +----------------------------------------------------------------------------+
+ |          URL:                                                              |
+ +============================================================================+
+ |                              DESCRIPTION                                   |
+ In Xerces-C 1.4, when ReaderMgr creates a stream through the
+ makeStream() method call on an InputSource, the stream seems to be
+ leaked if it throws an exception during it's readBytes method call. I
+ couldn't find a bug filed against this and was wondering if it has
+ been fixed in 1.5.1?
+ 
+ Cheers,
+ Brian

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to