Fatal error upgrading from 3.8.10 to 3.8.11

[Orange20]

We do indeed have a very large forum. With pictures in the file system our database is around 7.2GB. We have around 200k threads and 7.3mil posts. There is nothing in our server config that would limit 128MB. As I mentioned we upped the limits. The limit is somehow being invoked within the VB code.

I'd really like to stick with 3.x rather than upgrading to 4.x. The error is generated when working on vbvisitormessage and vbipdata tables.

Can you offer any suggestions on how we can overcome this issue?

--------------- Added [DATE]1494805081[/DATE] at [TIME]1494805081[/TIME] ---------------

Paul M.

Please forgive the double-post.

I have successfully upgraded from 3.8.10 to 3.8.11 using our database on a test server following this process.

/includes/class_xml.php

Find:

ini_set('memory_limit', 128 * 1024 * 1024);

Replace with:

ini_set('memory_limit', '-1');

Thanks again for your advice. Your comments above about ini_set inspired this solution.

Do you think it OK to upgrade the live server in this way? If so, would it be sensible to revert the code changes once the upgrade has completed?