Whenever I use apr_dbd_get_driver to get a driver, it will clean up nicely if the driver exists, but leak a few kb every time it fails, potentially resulting in MB upon MB of trash piling up in the memory banks.

I've tested with the following snippet that would simulate an apache httpd module starting up:

//--------------------------------------------
static void register_hooks(apr_pool_t *pool) {
    int x;
    int rc;
    apr_pool_t *POOL;
	apr_dbd_driver_t* driver;
	
    module_init(pool);
    ap_hook_handler(plua_handler, NULL, NULL, APR_HOOK_LAST);
    
    for (x=0;x<3000;x++) {
        POOL = 0;
		driver = 0;
        apr_pool_create(&POOL, pool);
        apr_dbd_init(POOL);
        rc = apr_dbd_get_driver(POOL, "nonexistentdriver", &driver);
        apr_pool_clear(POOL);
        apr_pool_destroy(POOL);
    }
    
}
//--------------------------------------------

If I replace the "nonexistentdriver" element with, per se, "odbc" or "sqlite3", it will load the driver and clean up nicely with not a drop to spare, but when I use a driver name that it cannot load, it will continue to use new memory, in this case upwards of 30-40MB for those 3,000 attempts in the above snippet.

Is this a bug, and if not, how do I resolve it, so it won't gobble up all my memory?