There are many programs to help you find the file referencing that symbol, but will do you no good. Freallocd is not a standard/common function, TMK, and not one a search turns up anything for, but is surely just a customized implementation of a realloc. It's new to me, but apparently frealloc is a name of a realloc optimized for key-value lists, and seems to supported by Oracle, a hodge-podge of BI software suites, and some compilers. I'm 99% sure that you will not find anything useful by locating it in some files.
Realloc (re-allocate) functions allocate a new block of memory, copy the old block's data into it, then return the location of the new block. If it cannot allocate the new memory, it will fail. I think it's a safe assumption that this freallocd is working as designed. Your problem is surely one of these:
1. Running into address space fragmentation problems (nothing you can fix, except by restarting the program, most likely)
2. Running into address space size limits (2GB, minus some overhead, for 32-bit programs)
3. Running into physical memory limits (exceedingly unlikely, and you would have a lot of page file thrashing, losing hours of work in the process--yes, even with an SSD--were this the case).
As old as it is, it's probably 32-bit, and you probably are starting to run out of memory during some data processing task. When I first replied, I did a bit of Google searching, and found the use of recursive functions weren't uncommon with the program, and did sometimes cause issues with running out of memory. Changing the code your specific use case runs, to do work in smaller chunks, or migrating to different software, are likely your only practical options.