I got a good one of these recently - in an inner nested loop we were using
cfparam to default a variable to a struct if it didn't exist. Because the
struct in the default attribute was always being created regardless of whether
or not it was needed, and the loop was executing 100s of 1000s of times
(building an index structure) we were allocating memory for structs faster than
the garbage collector could increase the heap size, and got errors like this.
Simply swapping to an if statement and a cfset fixed the problem.
Lesson: look for variables being created in code that runs a lot, and try to
minimise it.
Robin
ROBIN HILLIARD
Chief Technology Officer
ro...@rocketboots.com.au
RocketBoots Pty Ltd
Level 11
189 Kent Street
Sydney NSW 2001
Australia
Phone +61 2 9323 2507
Facsimile +61 2 9323 2501
Mobile +61 418 414 341
www.rocketboots.com.au
On 25/08/2010, at 1:25 AM, Dale Fraser wrote:
> Anyone explain what can be done about this or the possible causes
--
You received this message because you are subscribed to the Google Groups
"cfaussie" group.
To post to this group, send email to cfaus...@googlegroups.com.
To unsubscribe from this group, send email to
cfaussie+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/cfaussie?hl=en.
