You may be seeing the profiler creating extra copies of buffers and images. The profiler does this in order to run the test program repeatedly. To minimize the number of copies, please only mark buffers and images with the read and write flag (this is the default) where necessary. Flagging additional buffers or images will cause unnecessary extra copies to be made by the profiler.
If we can have a copy of your test program, we'll look and see if we have a problem that we can fix. Please send it to firstname.lastname@example.org, if you can.
Thank you. We received the test case. We can confirm that when running under the profiler, the test application is using about 1.8 GB RAM. It ran to completion though (on a 4 GB machine, Win7 64 bit) and didn't crash (the execution order was upto 10000 which is the limit in the profiler). We will investigate whether the memory usage is normal (due to the extra copies required by the profiler for the application) or not.
Which OS and GPU are you using?