On Sat, Apr 18, 2015 at 11:05 PM, Rabbi David Botton <[email protected]> wrote: > If you are using dynamic you shouldn't be deallocating manually. If you do > then when the garbage collection starts with App.Console is finalized it > will try to deallocate already deallocated blocks of memory.
Yeah, that was a mistake on my part. I wasn't able to edit it out afterwards. Thanks! > Unless you have extreme memory constraints, just overwrite the pointer since > the parent view will take care of things or do not use dynamic and > deallocate on connection close. I don't have any memory constraints per say, but something about allowing the list of elements to grow indefinitely like that doesn't sit well with something inside of me. I know practically it won't make a difference...I'm just weird like that. I'll probably go something similar to the 2nd route you mentioned. Thanks again! ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ Gnoga-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gnoga-list
