For the document attached below, wvWare was
consuming more than 1.7GB (it was increasing). The
problem is a kinda inconsistent with Windows 2000.
Release build of the library does behave normally some
times. But in the debug build, it was consistently leaking
The problem is identified inside libole2/ms-ole.c: read_pps
(..) function. Essentially, while clearing the root chain,
there was a tangling pointer coming in. I have added a
chain block checking routine to avoid the problem.
Log in to post a comment.