Hi Michael, At present fixing of UBA-7191 is not on the agenda for the following reasons:
1. There is a work around 2. ULC caches templates for various renderers on the client to optimize traffic. Normally, there is a small set of renderers that are used for a given table. So if you change a few renderers out of that set the leak won't be large. However, the problem may become significant if you have a large number of different renderers and you are changing a lot of them. Could you please tell me in what way you are defining and changing the renderers in your application? Are you encountering a big memory leak? Thanks and regards, Janak >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] Behalf Of McWhirter, >Michael >Sent: Tuesday, June 05, 2007 12:41 AM >To: [email protected] >Subject: [ULC-developer] ULCTable memory leak > > >We are currently using the workaround for the ULCTable memory leak >(UBA-7191). Is there any idea on when this bug might be fixed? > >Thanks, > >Michael McWhirter >Programmer/Analyst >Macomb ISD >(586)228-3379 > ><This message has been scanned for viruses by a Barracuda Spam Firewall.> >_______________________________________________ >ULC-developer mailing list >[email protected] >http://lists.canoo.com/mailman/listinfo/ulc-developer _______________________________________________ ULC-developer mailing list [email protected] http://lists.canoo.com/mailman/listinfo/ulc-developer
