• Show log

    Commit

  • Hash : c7c526d6
    Author : Kevin Puetz
    Date : 2020-01-13T18:49:01

    Fix memory leak when shared libxml.dll is unloaded
    
    When a multiple modules (process/plugins) all link to libxml2.dll
    they will in fact share a single loaded instance of it.
    It is unsafe for any of them to call xmlCleanupParser,
    as this would deinitialize the shared state and break others that might
    still have ongoing use.
    
    However, on windows atexit is per-module (rather process-wide), so if used
    *within* libxml2 it is possible to register a clean up when all users
    are done and libxml2.dll is about to actually unload.
    
    This allows multiple plugins to link with and share libxml2 without
    a premature cleanup if one is unloaded, while still cleaning up if *all*
    such callers are themselves unloaded.
    

  • README

  •                   XML toolkit from the GNOME project
    
    Full documentation is available on-line at
        http://xmlsoft.org/
    
    This code is released under the MIT Licence see the Copyright file.
    
    To build on an Unixised setup:
       ./configure ; make ; make install
       if the ./configure file does not exist, run ./autogen.sh instead.
    To build on Windows:
       see instructions on win32/Readme.txt
    
    To assert build quality:
       on an Unixised setup:
          run make tests
       otherwise:
           There is 3 standalone tools runtest.c runsuite.c testapi.c, which
           should compile as part of the build or as any application would.
           Launch them from this directory to get results, runtest checks 
           the proper functionning of libxml2 main APIs while testapi does
           a full coverage check. Report failures to the list.
    
    To report bugs, follow the instructions at: 
      http://xmlsoft.org/bugs.html
    
    A mailing-list xml@gnome.org is available, to subscribe:
        http://mail.gnome.org/mailman/listinfo/xml
    
    The list archive is at:
        http://mail.gnome.org/archives/xml/
    
    All technical answers asked privately will be automatically answered on
    the list and archived for public access unless privacy is explicitly
    required and justified.
    
    Daniel Veillard
    
    $Id$