Mario & Luigi: Paper Jam | crash when entering battle with Paper Mario

Issue:
Whenever I attempt to enter a battle, the emulator stutters and crashes. I tried with paper enemies and normal enemies; this only started occurring with Paper Mario in the party.
I have updated my graphics drivers, even though my laptop is a 2017 model.

System Information

  • Operating System: Windows 10 Pro
  • CPU: Intel i7-7200u 2.5GHz
  • GPU: Intel HD Graphics 620
  • Citra Version (found in title bar): 5620327
  • Game: Mario and Luigi: Paper Jam
  • Screenshot of Issue (include the full Citra window including titlebar):

Log:
EDIT: https://pastebin.com/pR3RD79q (New log)
https://pastebin.com/JPMsKN7j (OLD)

This is already a known issue and it has been reported before. https://github.com/citra-emu/citra/issues/2910

No. This is a different bug, as I was able to get past the goomba stack and acquire Paper Mario. It was only after I had Paper Mario in my party where I was unable to battle any entity.

I’m saying that both crashes are caused by the same thing:

[ 28.874768] Render.OpenGL video_core/renderer_opengl/pica_to_gl.h:PicaToGL::BlendEquation:106: Unknown blend equation 5

[ 38.208760] Render.OpenGL video_core/renderer_opengl/pica_to_gl.h:BlendEquation:106: Unknown blend equat (your log cuts short because of the crash)

Also, I see some error messages regarding your usage of any GL hooking programs (Fraps, Dxtory or MSI Afterburner) with Citra, or the error is caused by bad / corrupted Intel HD drivers.

[ 0.689319] Render.OpenGL
video_core/renderer_opengl/renderer_opengl.cpp:DebugHandler:472: API ERROR 1280: Error
has been generated. GL error GL_INVALID_ENUM in (null): (ID: 173538523) Generic error

Huh, I’ll try again with a different graphics driver.

New crash log, with the new graphics driver. Even if the bug is functionally the same as the goomba wheel crash, why has the bug not been fixed if it has been known about since June?

https://pastebin.com/pR3RD79q

It is still cut off at the end, I don’t know how to prevent that.

This log is completely different from the other log I had and the one from the other issue.