Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can make an OutOfMemoryException by sending a modified form list property with an high index [SPR-8375] #13022

spring-projects-issues opened this issue May 25, 2011 · 1 comment
in: web status: duplicate


Copy link

@spring-projects-issues spring-projects-issues commented May 25, 2011

Ludovic Praud opened SPR-8375 and commented

How to reproduce the problem

With a ModelAttribute such as :

class Model {
    List<String> getItems();

With a JSP such as :

<form:input path="items[0]" />

within an HTML form.

POST the form with modified items attribute :


and wait, wait, wait until the OutOfMemoryException.

Incriminated code

org.springframework.validation.DataBinder.autoGrowNestedPaths is default true, it should be false instead.


In a controller :

public void initBinder(WebDataBinder binder) {

or using an implementation of WebBindingInitializer :

public void initBinder(WebDataBinder binder, WebRequest request) {

Affects: 3.0.5

Issue Links:

  • #12498 DataBinder should be able to define a different strategy for BeanWrapperImpl how autogrowing should handle gaps in collection properties ("duplicates")

1 votes, 3 watchers

Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented May 25, 2011

Ludovic Praud commented

Ok, it would be better to limit the growing of list and array instead of removing auto-growing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
in: web status: duplicate
None yet

No branches or pull requests

2 participants