I know how to work around it, the issue is whether this can be ignored and make into final release. I believe this memory leak is severe enough to have critical status and be handled with priority.
Cheers Karol Kevin McArthur-2 wrote: > > Karol, > > I suggest that if memory is a problem, that you either a) get more memory > (the leak is relatively small compared to gigs of memory on most systems) > or > b) write the application such that it works on a dispatch queue and a cli > script called once for each report. Either of these should workaround the > bug for now. > > K > ----- Original Message ----- > From: "Karol Grecki" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Sunday, June 17, 2007 5:53 AM > Subject: Re: [fw-general] Schedule for ZF 1.0.0 RC3 > > >> >> Pdf component was already "advertised" as major feature of ZF on few >> occasions. >> It would be a shame if this bug would make to final release considering >> it's >> severity. >> It's a major loss of function for anyone trying to generate many reports >> in >> batch. >> I'd keep it critical. And I'm not saying this just because I need it for >> my >> own project :) >> >> Cheers >> Karol >> >> >> Kevin McArthur-2 wrote: >>> >>> I can confirm the bug in ZPDF, however, I don't immediately see the fix. >>> Alex will likely have to fix the problem... In the mean time I would >>> probably reduce it's priority from critical to high as it's not a >>> showstopper for most. >>> >>> Kevin >>> >>> ----- Original Message ----- >>> From: "Bill Karwin" <[EMAIL PROTECTED]> >>> To: <[email protected]> >>> Sent: Saturday, June 16, 2007 2:25 PM >>> Subject: [fw-general] Schedule for ZF 1.0.0 RC3 >>> >>> >>> Hi, >>> >>> The ZF product has achieved a lot of maturation recently and everyone >>> has been working very hard. There have already been 47 issues fixed >>> since RC2! We're planning the final schedule for Zend Framework 1.0.0 >>> RC3. It's our hope that this RC3 will become the GA release, but of >>> course if there are critical issues with RC3 we'll fix them and make >>> another release candidate. >>> >>> NB: absence of a feature or component is not a critical issue. :-) >>> >>> We currently have a single critical bug open, which is a possible memory >>> leak in Zend_Pdf. >>> If anyone wants to help out by troubleshooting this issue, the bug id is >>> ZF-1559. >>> >>> Code-freeze for the ZF 1.0.0 RC3 release will begin on Friday June 22 at >>> 4:00pm PDT (June 23 12:00am GMT). >>> >>> Regards, >>> Bill Karwin >>> >>> >>> >> >> -- >> View this message in context: >> http://www.nabble.com/Schedule-for-ZF-1.0.0-RC3-tf3934133s16154.html#a11162592 >> Sent from the Zend Framework mailing list archive at Nabble.com. >> > > > -- View this message in context: http://www.nabble.com/Schedule-for-ZF-1.0.0-RC3-tf3934133s16154.html#a11165627 Sent from the Zend Framework mailing list archive at Nabble.com.
