Dear developers: Our product is close to sipping stage and we are doing stress tests on FS servers. We have now hit a dead end with our test results and running out of ideas. And the result is pointing to memory issues. We have ran our test on both FS 1.0.4 and 1.0.6 trunk with SIPP to do simply invite tests. Here is the test senario: Send 10,000,000 invites to our test server running FS 1.0.6 with fixed amount of invites per second. The xml dialplan simply bridge the call to an unknown/unregistered user like so (user/500001) and therefore FS would hang up once it doesn't find the user. When running the test, FS is steady, but the memory usage slowly piles up over time. The memory keeps adding up till it hit the ceiling, then FS crash. I don't understand what could be holding the memory and not releasing it since we are not doing anything special and the calls are not being answered. And I forgot to mention, through out the whole test, the CPU usage stays at about 35% . Please help Besides FS native test, we have created our own application module to run the same test. The app is written in C and basically what we did is to point the xml dialplan to the custom app. Inside our app , we are simply doing the same kind of test as the xml dialplan would do. The only thing we did for the stress test is the following code: switch_core_session_execute_application(session, "bridge", "user/500001"); Like the xml dialplan test, we are bridging the call to a unregistered user, so the call would hang up right away if system doesn't find the user. But the bizarre thing is this - the memory usage is about 7 ~ 8 times as much as we are running only xml dialplan. This I don't understand. Our app is calling the native FS C function to bridge the call , why would it use more memory than the xml dialplan... your input would be very much appreciated. thanks -- Henry Huang aka bbhenry VoIP & Open Source software Consultant