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 bu...@apache.org on 2001/04/18 17:01:42 UTC
[Bug 1368] New - improper DOMStringHandle locking
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1368
*** shadow/1368 Wed Apr 18 08:01:42 2001
--- shadow/1368.tmp.19845 Wed Apr 18 08:01:42 2001
***************
*** 0 ****
--- 1,24 ----
+ +============================================================================+
+ | improper DOMStringHandle locking |
+ +----------------------------------------------------------------------------+
+ | Bug #: 1368 Product: Xerces-C |
+ | Status: NEW Version: Nightly build |
+ | Resolution: Platform: All |
+ | Severity: Major OS/Version: All |
+ | Priority: High Component: DOM |
+ +----------------------------------------------------------------------------+
+ | Assigned To: xerces-c-dev@xml.apache.org |
+ | Reported By: maxwolf@cma.ru |
+ | CC list: Cc: |
+ +----------------------------------------------------------------------------+
+ | URL: |
+ +============================================================================+
+ | DESCRIPTION |
+ DOMStringTerminate (DOMString.cpp:1187) function is not thread safe since it
+ deactivates DOMStringHandle mutex in two steps. Assumption at the line 330 of
+ DOMString.cpp is not valid for current build (versions based on 1.4). So the
+ DOMStringTerminate could be called during the normal operations. If it happens
+ from several concurrent threads then process crashes with good probability.
+
+ We have either to make DOMStringTerminate thread safe or to create long live
+ DOMString in XMLPlatformUtils::Initialize.
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org