If the core that you already have is an ELF based core from Linux on some x86 based platform and your process used libc malloc, one way to understand what these objects are (temporary objects or leaks) is to use the free open source software https://github.com/vmware/chap to figure that out. After you have built chap you start it like this:
chap core-file-name
Then to answer your particular question issue the following commands from the chap prompt:
redirect on
show leaked
show anchored
show free
Then look in each of the 3 resulting text files for the pattern that you saw in the core. If the pattern is seen in the output from "show leaked", you have a leak. If it is seen in the output from "show anchored", the objects are likely held in some container, but there is still a possibility that it is leaked. If it is seen in the output of "show free", it is from a temporary allocation that now has been freed.
Alternatively, if you already know the virtual address of that pattern and want to see how it was used, after you have started chap on the given core you can just use the following command:
describe virtual-address-in-hexadecimal