From: "Schneider, Stuart" <Stuart.Schneider@pacificorp.com> Just wanted to pass along another update while trying to use PerLDAP on an NT4 system. After I started converting some of my scripts from Net::LDAPapi to the new modules, I came across a problem where the new library would blow up and return an "Error: Runtime exception" after performing between 200 to 5000 searches on the directory. I've since installed a C compiler on my system and have been seeing the exact same problem with v1.1 of the modules. I've managed to track the call down to the ldap_value_free call made at the conclusion of the ldap_search_s XS function call. As a temporary fix I've commented out the call to ldap_value_free in the API.xs file and my scripts now work perfectly (although I do notice a memory leak when running the script - after about 20,000 queries, the script is consuming an additional 5meg of memory). What additional information can I provide to help track this down? Personally, I'm leaning towards the possibility that this is a bug in Netscape's LDAP library for the Win32 platform since the same code works perfectly on my RedHat Linux system. Unfortunately, I have to run this on Win-NT. Stuart Schneider Stuart.Schneider@pacificorp.com

Setting all current Open Critical and Major to M3

Clearing "M" field since Directory product is not used for 5.0 specific project bug metrics and will mess up our queries on milestones.

Closing this bug, I think we've covered all free()'s with if statements.

Adding crash keyword