core dumps for anything are not normal behavior. The only ways this could happen:
One process is signaling another with SIGABRT or some other sinal that forces a core dump. This is odd behavior and I've not seen it.
Some process itself had a bus error or a segfault, which means there is a problem with the process code. Or a shared library. This sometimes happens when there are upgrades or patches applied to a sytem.
It may also be that the process cannot do what it is supposed to do - maybe it has been started at the wrong time. Or run on a system that is not configured to do what the process expects. Or a control file for the process is corrupted....
Yes, you need to research it and fix it if possible.