On Fri, 22 Feb 2013 16:30:25 +0000 (GMT), Michael Drake wrote: > > I think I've tracked this down to a bug (or "implementation feature", > > perhaps) in OS4's newlib realloc() function. > > > If I allocate 10MB of memory in 64 byte chunks using realloc(), around > > 400MB of RAM gets eaten up, rather than the expected 10MB. > > Does it behave any better now? I've increased the step size.
Doesn't seem to have made an awful lot of difference, unfortunately. I do seem to have finally convinced the PTB that there is a problem though. > In other news, the Amiga ami_file_save_req() behaviour needs attention, > because browser_window_get_selection() now returns a pointer to a char * > string that the client must free, rather than the old textplain/html > struct selection object. I think I've obliterated struct selection* from the frontend now. Chris
