2002.08.20 07:31 "memory allocation", by Peter Majer
-
2002.08.20 16:13 "RE: memory allocation", by Roger Bedell
-
2002.08.20 20:48 "OT: large memory allocation in Windows", by Dante Allegria
-
2002.08.21 08:34 "Re: OT: large memory allocation in Windows", by Rob van den Tillaart
-
2002.08.21 11:30 "Re: OT: large memory allocation in Windows", by Peter Majer
-
2002.08.21 13:47 "Re: OT: large memory allocation in Windows", by Rob van den Tillaart
- 2002.08.21 16:05 "Re: OT: large memory allocation in Windows", by Bob Friesenhahn
-
2002.08.21 20:47 "Re: OT: large memory allocation in Windows", by Peter Nielsen
-
2002.08.22 08:33 "Re: OT: large memory allocation in Windows", by Andreas R. Kleinert
-
2002.08.22 15:30 "RE: OT: large memory allocation in Windows", by Roger Bedell
-
2002.08.22 16:29 "Re: OT: large memory allocation in Windows", by Chris 'Xenon' Hanson
- 2002.08.22 17:20 "RE: OT: large memory allocation in Windows", by Roger Bedell
- 2002.08.22 17:33 "Re: OT: large memory allocation in Windows", by Peter Montgomery
-
2002.08.22 16:29 "Re: OT: large memory allocation in Windows", by Chris 'Xenon' Hanson
- 2002.08.22 15:59 "RE: OT: large memory allocation in Windows", by Ed Grissom
-
2002.08.22 15:30 "RE: OT: large memory allocation in Windows", by Roger Bedell
-
2002.08.22 08:33 "Re: OT: large memory allocation in Windows", by Andreas R. Kleinert
-
2002.08.21 13:47 "Re: OT: large memory allocation in Windows", by Rob van den Tillaart
- 2002.08.21 11:48 "Re: OT: large memory allocation in Windows", by Peter Nielsen
-
2002.08.21 11:30 "Re: OT: large memory allocation in Windows", by Peter Majer
- 2002.08.22 18:00 "Re: OT: large memory allocation in Windows", by Bob Friesenhahn
-
2002.08.21 08:34 "Re: OT: large memory allocation in Windows", by Rob van den Tillaart
-
2002.08.20 20:48 "OT: large memory allocation in Windows", by Dante Allegria
2002.08.21 11:30 "Re: OT: large memory allocation in Windows", by Peter Majer
Dear Rob,
the problem of heap fragmentation cannot be that seldom. what are the standard proven ways to solve it? i am quite surprised about the lack of information on this topic.
the solutions that spring to my mind are:
- 64 bit compilation
- reorganizing memory requirements of the application such that contiguous large blocks are not necessary. E.g. store the data of a large image as an array of rows.
- make sure the application can run for ever with the memory that can be allocated in the beginning. In case of applications working with images, we might allocate the one image we load plus another one for some processing purposes and make sure that we never ever free these and need to allocate new large blocks.
Also, I have been thinking about the third point you mention as a solution as well. Does anyone by chance know if there is an autopointer class out there that is of help with memory reorganization?