You say this and immediately contradict yourself afterwards.
I’m aware that you mentioned this. I’m also sure that I adressed this:
Since you appear very attached to these version that do work for you at the moment. Let me explain the issue a bit further:
This is not an issue with Citra. The 5 latest Canary versions that were released changed nothing that can crash literally anything. I should know, I’ve handled every support case that came in during the release times of those versions. The issue can therefore not be caused by Citra itself. Meaning there’s an issue with your configuration or set-up. Now that we’ve established that the problem isn’t Citra itself. Let’s move on to what the issue actually is.
Like I mentioned earlier:
This is a well known issue with your specific iGPU. The symptoms match, the log file matches and the observations you made, with one Citra version working and the next deciding not to without having any real reason not to, match as well.
To ilustrate the point, I have an old laptop with the same generation of iGPU that you have. An Ivy Bridge iGPU: Intel HD 4000. This iGPU has the exact same issues. I even fired it up for you and tried to play the latest Citra versions. The latest Canary build worked perfectly fine, The latest Nightly build froze my games on launch every single time. So that’s what I meant with randomly crashing. My observation is the inverse of yours, yet the issue is identical.
I then switched from my latop’s iGPU to my laptop’s dedicated NVIDIA GPU, and now both the latest Canary and Nightly run without issues. Combine the information above with the fact that, like I mentioned already, this is the most common support issue we get on the forums, and all of those support requests have different Citra builds that for some reason refuse to work, and the only thing that all of these support requests have in common is an Intel Ivy Bridge iGPU, I think you can see the point.
Nightly 1392 and below are the only Citra versions on which the OpenGL drivers of these Ivy Bridge iGPUs don’t just randomly decide to shit themselves after a while. This is why I recommended this build over using a Nightly or Canary build that currently still works for you. There’s a good chance that at some point, it won’t work for you anymore and it would suck if it corrupted your save data to go along with it (and before you ask, yes, that has happened a couple times before).
What you end up doing with this information is up to you. I still highly recommend you to use the Nightly 1392 build I linked earlier for the reasons metioned above. But yea, don’t say I didn’t warn you.