Hi all,
I'm looking for beta testers for a 1.04 release (finally :-P).
The beta release is labelled v1.03_04, and is available for download
from http://www.robmay.me.uk/win32gui/.
Release Notes and a Perl 5.8 PPM are linked at the bottom of the page.
Please download and give it a spin. Feed
Huraah! Proof I`m not going mad :) I`d be more than happy to test it out.
/me goes off to backup current files.
Steve
I've had a quick look at the source, and it appears there is indeed a
leak, which matches your described symptoms:
- If there is no transparency in the image, then AlphaCOpyT
Steve,
Laurent in no longer maintaining WIN32::GUI::DIBitmap, and it's in the
Win32::GUI repository.
I've had a quick look at the source, and it appears there is indeed a
leak, which matches your described symptoms:
- If there is no transparency in the image, then AlphaCOpyToDC uses
exactl
OK, some more on this memory leak issue.
If I change the code from using AlphaCopyToDC() to using CopyToDC()
(Havent changed anything else in the code at all), the memory leak
stops... completely. If I put AlphaCopyToDC() back in again, the leak
reappears.
Odd i`ll try to write a small c
Strict - yes, all the time
warning - most of the time :)
I think I have tracked the leak down to the window_paint routine, and
specifically to the DIBitmap routine AlphaCopyToDC(). I need to do some
more fixed tests, but to me it looks like a problem with Alpha channels
in DIBitmap structures,
are you already using use strict? if not use it and cleanup every warning.
threads generally have all kinds of memory problems so if ur using
threads life becomes very difficult.
Steve Loughran wrote:
Hi all
Not strictly a win32-gui related question. How would I go about tracking
down my me
Hi all
Not strictly a win32-gui related question. How would I go about tracking
down my memory usage in a perl script? I have a small memory leak in my
code somewhere, but no idea where to start looking for clues.
Anyone got any pointers or tips?
Steve
7 matches
Mail list logo
