There’s a couple of possibilities I see from the log and some Googling/research:
The occurrence of this fault is nothing new or unique, as it has happened before with a reference to a “font” when in actuality it was referencing the wrong folder location and it causes the game to crash within Retroarch. Also, there are certain spots within the game itself that not only cause Retroarch-PPSSPP to crash, but also cause the stand-alone version of PPSSPP to crash as well. The log references the fact that it overruns the memory and adjusts the limit of the memory overrun buffer on the fly, which I found weird to do and figured was a precursor of things to come.
When you look closer at the log, I noticed that some of the original encryption blocks from Sony’s old encryption algorithms make an appearance in the log. Not enough to block you from playing the game and you can correct it as part of a CRC check, but you would have to be consciously not having your buffer fill up with other references from not being able to resolve previous frames (which is also in the log as well). The core was having too many unresolved pieces of info and gave the hell up. BOOM! Crash.
The buffer overrun correction was implemented in the stand-alone version of PPSSPP later on but has not been implemented in Retroarch yet (which explains why it works in the stand-alone versions of PPSSPP, but not the RA/Lakka versions). The current version of PPSSPP is 1.5.4 while the Lakka one is 1.4.2 on the 2.1 revision of Lakka. Dissidia is STILL generating problems on PPSSPP in its stand-alone current iteration, so I don’t think you’re out of the woods yet.