RE: win32lib v0.57.4 released
- Posted by jordah ferguson <jorfergie03 at yahoo.com> May 07, 2002
- 384 views
Hi Derek, I think this is the resource leak Thomas Parslow has been mentioning about. It is surely a resource leak because it takes some time before it appears. It says ezCreateFont:save Font failed. I have experienced this problem since ver 55.5 What i'm doing: I am simply writing and drawing on a pixmap which i later copyBlt on a Win32lib Bitmap Control. this is a sample of the garbage returned after the crash c:\mail\win32lib.ew:201 in procedure fShowError() attempt to divide by 0 pParams = {{101'e',122'z',67'C',114'r',101'e',97'a',116't',101'e', 70'F',111'o',110'n',116't',58':',83'S',97'a',118'v',101'e',68'D',67'C', 32' ',102'f',97'a',105'i',108'l',101'e',100'd',46'.'},491} pMode = 2 lErrCode = 491 lResponse = 1 lStyle = 16 s = {101'e',122'z',67'C',114'r',101'e',97'a',116't',101'e',70'F',111'o', 110'n',116't',58':',83'S',97'a',118'v',101'e',68'D',67'C',32' ',102'f', 97'a',105'i',108'l',101'e',100'd',46'.'} ... called from c:\mail\win32lib.ew:212 in procedure abortErr() pParams = {{101'e',122'z',67'C',114'r',101'e',97'a',116't',101'e', 70'F',111'o',110'n',116't',58':',83'S',97'a',118'v',101'e',68'D',67'C', 32' ',102'f',97'a',105'i',108'l',101'e',100'd',46'.'},491} ... called from c:\mail\win32lib.ew:5298 in function EzCreateFont() id = 3 pDC = 4466 faceName = {84'T',105'i',109'm',101'e',115's',32' ',78'N',101'e',119'w', 32' ',82'R',111'o',109'm',97'a',110'n'} iDeciPtHeight = 80'P' iDeciPtWidth = 0 iAttributes = 1 fLogRes = 0 logfont = 0 hdc = 4466 cxDpi = <no value> cyDpi = <no value> hFont = <no value> lf = 7677836 pt = 7677900 tm = <no value> savedDC = 0 mset = 7677820 boldFlag = <no value> italicFlag = <no value> underlineFlag = <no value> strikeOutFlag = <no value> lWidth = 0 lEscapement = 0 lOrientation = 0 lCharSet = 0 lOutPrecision = 0 lClipPrecision = 0 lQuality = 0 lPitchAndFamily = 0 ... called from c:\mail\win32lib.ew:5372 in function assignFont() id = 3 fontID = <no value> result = <no value> hdc = 4466 lifetime = <no value> ... called from c:\mail\win32lib.ew:5884 in function queryFont() id = 115's' request = 524455 args = {7677800,15,7677784} useId = 3 hdc = <no value> result = <no value> saved = {{},10,0,0} ... called from c:\mail\win32lib.ew:5939 in function getTextExtent() id = 115's' text = {{115's',115's',115's',115's',115's',100'd',102'f',102'f',102'f', 102'f',102'f',102'f',102'f',32' ',32' '}} Make Progress...or stand aside! jordah Ferguson jorfergie03 at yahoo.com Derek Parnell wrote: > > Thomas Parslow (PatRat) wrote: > > > - "by Thomas Parslow". GDI resource leak using wPuts and queryFont > > > removed. > > > > Hi, > > > > This bug still seems to be present, applying the fix I posted before > > still works though... > > > > > > http://www.rapideuphoria.com/cgi-bin/esearch.exu?fromMonth=4&fromYear=7&toMonth=4&toYear=7&postedBy=thomas+parslow&keywords=queryFont+wPuts > > > > > That's weird Thomas. I tested it and got no resource leakage. Maybe my > testing process is flawed. How exactly are you seeing the resource > leakage? > As for your fix, yes it worked but I needed a more generic way of doing > > it, so I adapted your code to catch all font leaks, now and in the > future. (Or so I thought). > ----------- > Derek. > >