ispcp-apache-logger bugs ?

[blocker]

hi, i have a test server with 32Gb memory system, the os is FreeBSD, using ispcp as control panel, I setup a domain then we hammering that domain with a lot of connection until the load to that server goes up to 100 sometimes to 300, when load become 250-300 and processor usage 87% specific at system resource that handle I/O ( I think, base on top ) the log become corrupted but if i disable ispcp-apache-logger, the log that apache created still intact ( in this case /var/log/httpd-access.log) here is files in log dir when goes corrupted

-rw-r--r-- 1 root www 201 May 4 13:50 %3dforid%253a11%26ie%3xxx-8%26q%3dxxx-access.log
-rw-r--r-- 1 root www 202 May 4 11:02 2903-access.log
-rw-r--r-- 1 root www 277 May 4 13:49 2bxxx%2bdbs%xxx.com-access.log
-rw-r--r-- 1 root www 257 May 4 11:01 com-access.log
-rw-r--r-- 1 root www 410 May 4 13:49 default-access.log
-rw-r--r-- 1 www www 856251 May 6 08:03 default-error.log
-rw-r----- 1 root wheel 52266790 May 6 08:42 xxx.com-access.log


the real log is just xxx.com-access.log and defaul-error.log

so i wonder is this perl's bug or Os memory spesific bug or the program it self when dealing with such condition. somebody can give me a clue ?