[Regression] Big profile build makes StackOverflowError

[youngho]

Recently a big profile build makes StackOverflowError?.

I attach build.log and test profile.

Actually, my real proflie is about 2.5 times bigger than the test profile. But There was not happened the StackOverflowError? before.

[youngho]

One thing I missed. If a test profile is a little smaller than test profile, than the build works well.

[bill]

Probably from the async loader work?

[Rawld Gill]

It is unlikely this is caused by AMD refactor since the error is occurring well after the transforms that make the modules look like pre-AMD modules and, according to the report, the transform works with a smaller profile.

Please confirm what version of dojo you are using. Is it really v1.5? Trunk? If trunk, which revision?

[youngho]

I used trunk current revision.

When I wrote this ticket, I cound not find 1.6 version option in version selector. Sorry for confusion.

[Rawld Gill]

Replying to youngho:

I used trunk current revision.

When I wrote this ticket, I cound not find 1.6 version option in version selector. Sorry for confusion.

Could you please pull the latest--at least r23138 or later and try again. Also, if you have a problem, could you post the output from the build program.

Thanks!

[youngho]

Because of #11937 which I reported today, I could not build. After #11937 fixed, I will test with my real profile and post the result.

[youngho]

Hello rcgill,

Today I tested my build profile with the latest version.

But still StackOverflowError? happend. I attached the build.log

[youngho]

Build test log file with the latest svn version

[Rawld Gill]

The stack overflow is well after the AMD inverse transforms. James--could you take a look at the build log and see if it means anything to you?

[bill]

punting new-ish 1.6 tickets to 1.7

[Adam Peller]

is this no longer an issue with our new build system?

[bill]

Bulk update to assign BuildSystem? tickets to Rawld. Many of these are probably already fixed in 1.7.

[ben hockey]

youngho can you confirm if this problem still exists in 1.7

[bill]

Note that the test case is unusable because it references stuff from a non-existant easydesk directory.

(I tried running it and it went fine, except for that error.)

[trac-o-bot]

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!