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

Processing complex XSDs exhausts available memory #96

Open
dpf11 opened this issue Jan 30, 2020 · 1 comment
Open

Processing complex XSDs exhausts available memory #96

dpf11 opened this issue Jan 30, 2020 · 1 comment

Comments

@dpf11
Copy link

dpf11 commented Jan 30, 2020

I'm trying to use xsdgen on the SAML 2.0 XSD definitions. Specifically, saml-schema-assertion-2.0.xsd as found at:

https://docs.oasis-open.org/security/saml/v2.0/

I went through and manually downloaded the dependencies and ran:

xsdgen saml-schema-assertion-2.0.xsd xmldsig-core-schema.xsd xenc-schema.xsd

The result is that the process's memory starts ballooning until I had to kill it. On my system that was around 32GB of memory. When I ran it with the -vv flag it appears to be going in circles processing the files over and over. I don't know enough about the tool to say if it's stuck in a loop or some sort of NP-complete hell.

Go version: go version go1.13.6 linux/amd64

@droyo
Copy link
Owner

droyo commented Mar 21, 2020

This is probably a duplicate of #86 . Most likely one of those schema contain a recursive type definition, and xsdgen chokes on that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants