PASSED Manual Testing following the steps in my previous comment.

Reproduced on:
Tomcat 7.0 + MySQL 5. Portal 6.1.0 EE GA1.

After run the script, Console displays OutOfMemoryException error. And the script runs so slow.

Fixed on:
Tomcat 6.0 + MySQL 5. Portal 6.0.x.EE GIT ID: c66f63074decc74f2060464d300455883c70f68d.
Tomcat 7.0 + MySQL 5. Portal 6.1.x.EE GIT ID: 9db5d1166371a6e59e4ee4f7aa421f7e54f936f4.
Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 43d6b6844cd6f1e71b0b860d66b16a7b24889865.

After fix, the script runs fast and no OutOfMemoryException error in console any more.

Steps to reproduce:
1. Download the attached test.java file.
2. Startup tomcat.
3. Add Web Content Display portlet. Try to put

in web content body(click on source). (This is just an fast way to reproduce by putting huge worlds in the url.)

3. Navigate to the test.java folder and open a command window, use command line "javac test.java" and "java test" to run the script to hit the page repeatly.
4. Wait for the scritp run.
5. After a while you will see Out of memory error displays in console. For 6012EE, it should be like:

After fix, the script runs very fast.

Committed on:
Portal 6.2.x GIT ID: 3e6ceb7664615666aa2d6afd9c501b1d49ca6685.

Adding configurable thresholds:

I understand, but the same issue is true of simply storing these parameters in the PortletPreferences entity without putting it in the session because the PortletPreferences object is cached!

Perhaps there should be a threshold for the number of attributes stored in the preference, as well as for the size of the values themselves?