Do you want to continue to pursue the issue you've had with v3.6?

There are 3 flavors: Beta 1, 2 and 3. #1 was replaced with #2 under duress. Which have you been using?

Another 'fresh light-bulb', is to put the same version you've seen the issue with on a localhost, and see if it can be reproduced.

We're not hearing anything from Dev these days ... but still, to clearly ID a problem on your site would be a good thing. If you can 'crowd-source' bug-chasing this way, that would be a round on the house, eh?

Notably, we can set limits for PHP memory and other resources, on a localhost.

[I got a 500 Internal, the first time I hit this URL in my e-mail. I then trimmed it to the homepage, and it came up.]