You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by "Boris Kolpackov (JIRA)" <xe...@xml.apache.org> on 2009/11/17 14:24:39 UTC
[jira] Closed: (XERCESC-501) Xerces hangs in ThrowXML
[ https://issues.apache.org/jira/browse/XERCESC-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Kolpackov closed XERCESC-501.
-----------------------------------
Resolution: Invalid
Assignee: (was: Xerces-C Developers Mailing List)
Can you try to reproduce this problem with the latest release? If it is still there, can you reopen this bug and provide a test case?
> Xerces hangs in ThrowXML
> ------------------------
>
> Key: XERCESC-501
> URL: https://issues.apache.org/jira/browse/XERCESC-501
> Project: Xerces-C++
> Issue Type: Bug
> Components: Utilities
> Affects Versions: 1.7.0
> Environment: Operating System: Windows NT/2K
> Platform: PC
> Reporter: Mikael Widenfalk
>
> I have several threads (CWinThread) that use Xerces. Sooner or later one
> specific thread gets stuck in ThrowXML. The exact point varies depending on what
> I send in systemID. This is one example:
> void XMLURL::setURL(const XMLCh* const baseURL
> , const XMLCh* const relativeURL)
> {
> cleanup();
> // Parse our URL string
> parse(relativeURL);
> //
> // If its relative and the base is non-null and non-empty, then
> // parse the base URL string and conglomerate them.
> //
> if (isRelative() && baseURL)
> {
> if (*baseURL)
> {
> XMLURL basePart(baseURL);
> if (!conglomerateWithBase(basePart, false))
> {
> cleanup();
> ----> ThrowXML(MalformedURLException,
> XMLExcepts::URL_RelativeBaseURL);
> }
> }
> }
> }
> [ baseURL = "Client" relativeURL = "Information-1-0.dtd" ]
> The calltree proceeds with:
> MSVCRTD!__CxxThrowException@8
> KERNEL32!77e989d1()
> so there are no more clues there I guess. The CPU is at 0% and it appears as
> though everything is stuck in some mutex.
> I've made a (large) test program that spawns 50 threads and parses 50 DTD'd XML
> documents in each and it also occasionally gets stucks.
> Brief facts of the case are:
> * Single thread single point of initialization.
> * Uses SAX.
> * New parser, etc. for each document read.
> * Uses MemBufInputSource.
> * Uses MS VS6 sp5.
> Sorry if this provides little clue as to what goes on. Please contact me for
> more specfic information, if needed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org