-
Show log
Commit
-
Hash : fc26934e
Author :
Date : 2023-09-21T23:29:18
memory: Fix memory debugging with Windows threads On Windows, malloc hooks can be called after the final call to xmlCleanupParser in various tests. This means that xmlMemMutex can still be accessed if memory debugging is enabled, so the mutex should not be cleaned. This also means that tests may report spurious memory leaks on Windows. The old implementation avoided the issue by keeping track of all global state objects in a doubly linked list, so they could be cleaned during xmlCleanupParser. But as far as I can tell all memory will be freed eventually, so this is mostly an issue with our test suite.
-
Files
- Makefile.am
- attribs.py
- build.py
- compareNodes.py
- ctxterror.py
- cutnpaste.py
- dtdvalid.py
- error.py
- inbuf.py
- indexes.py
- input_callback.py
- invalid.xml
- nsdel.py
- outbuf.py
- push.py
- pushSAX.py
- pushSAXhtml.py
- reader.py
- reader2.py
- reader3.py
- reader4.py
- reader5.py
- reader6.py
- reader7.py
- reader8.py
- readererr.py
- readernext.py
- regexp.py
- relaxng.py
- resolver.py
- schema.py
- serialize.py
- setup_test.py
- sync.py
- test.dtd
- thread2.py
- tst.py
- tst.xml
- tstLastError.py
- tstURI.py
- tstmem.py
- tstxpath.py
- valid.xml
- validDTD.py
- validRNG.py
- validSchemas.py
- validate.py
- walker.py
- xpath.py
- xpathext.py
- xpathleak.py
- xpathns.py
- xpathret.py
-
Properties
