Topic: "Out of memory at line 100" - Windows Error after 2.2.2 upgrade

[David]

SMF Version: 1.1.9
SP Version: 2.2.2 Upgrade

Description of problem:

After upgrading to 2.2.2 from 2.2.1, all of my members are experiencing an error in their IE browsers when loading any page of the forum. The pop-up says "Out of memory at line 100".

This does not seem to be a PHP or MySql memory leak or issue. PHP5 is set to accept up to 32 MB which is plenty. I am using Abyss Web Server version 2, Pro Edition, under Windows XP with 2GB of RAM.  Never had a problem like this before with SP.  I'm currently running SP on 3 sites, and the only ones showing this error are the 2 sites that I just upgraded to 2.2.2. only 2 hours ago.

Here is a screenshot of what my members and I see on every page of the site after SP tries desperately to load:

Can I uninstall this mod and go back to the 2.2.1 version SAFELY until this is resolved? I would SO RATHER not do that if I can fix the issue, instead. Your latest release offers bug fixes to many other issues and I would hate to go backward if I can avoid it.  One of the sites using 2.2.2 is live, though, and we have clients going there...so a speedy resolution is critical.

Here is a link to one of the sites:

http://www.helpinghandsoutreach.net

Any help would be appreciated. I have said it before, but I will say it again, I wil never settle for less than Simple Portal. It's a great portal system developed by people that I hold in very high regard.

Thanks for listening,

David

[[SiNaN]]

Hello David,

First of all, try this:

Sources/SPortal1-1.php
Find:
$modSettings['sp_resize_images'] = true;
Replace:
$modSettings['sp_resize_images'] = false;

If that doesn't solve the issue, try renaming the Themes/default/sp_pngfix.js file to something else.

[David]

Hello David,

First of all, try this:

Sources/SPortal1-1.php
Find:
$modSettings['sp_resize_images'] = true;
Replace:
$modSettings['sp_resize_images'] = false;

If that doesn't solve the issue, try renaming the Themes/default/sp_pngfix.js file to something else.

Warning: Unprofessional side of me about to come out for a second:

DUDE!!!  YOU ROCK!!!

How do you do that, man?  How do you see a little error that could be anywhere...and go "oh yeah...that's the shlinginflonger recursive manual overide, located in the source file, line 237...just rewrite the code so that the memory explodes and the computer begs for mercy...no problem!"?

That's TWO favors I owe you, my friend.

Problem solved. Thank you very much.

David