Opened 9 years ago

Closed 7 years ago

#11900 closed defect (invalid)

[Regression] Big profile build makes StackOverflowError

Reported by: youngho Owned by: youngho
Priority: low Milestone: 1.8
Component: BuildSystem Version: 1.5
Keywords: big profile Cc:
Blocked By: Blocking:

Description

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.

Attachments (3)

build.log (4.1 KB) - added by youngho 9 years ago.
easydesk-test.profile.js (32.7 KB) - added by youngho 9 years ago.
build.zip (52.2 KB) - added by youngho 9 years ago.
Build test log file with the latest svn version

Download all attachments as: .zip

Change History (18)

Changed 9 years ago by youngho

Attachment: build.log added

Changed 9 years ago by youngho

Attachment: easydesk-test.profile.js added

comment:1 Changed 9 years ago by youngho

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

comment:2 Changed 9 years ago by bill

Milestone: tbd1.6
Owner: changed from James Burke to Rawld Gill

Probably from the async loader work?

comment:3 Changed 9 years ago by Rawld Gill

Status: newassigned

comment:4 Changed 9 years ago by 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?

comment:5 Changed 9 years ago by 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.

comment:6 in reply to:  5 Changed 9 years ago by 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!

comment:7 Changed 9 years ago by 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.

comment:8 Changed 9 years ago by youngho

Hello rcgill,

Today I tested my build profile with the latest version.

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

Changed 9 years ago by youngho

Attachment: build.zip added

Build test log file with the latest svn version

comment:9 Changed 9 years ago by Rawld Gill

Owner: changed from Rawld Gill to James Burke
Status: assignednew

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?

comment:10 Changed 8 years ago by bill

Milestone: 1.61.7

punting new-ish 1.6 tickets to 1.7

comment:11 Changed 8 years ago by Adam Peller

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

comment:12 Changed 8 years ago by bill

Owner: changed from James Burke to Rawld Gill

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

comment:13 Changed 8 years ago by ben hockey

Owner: changed from Rawld Gill to youngho
Priority: highlow
Status: newpending

youngho can you confirm if this problem still exists in 1.7

comment:14 Changed 8 years ago by 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.)

comment:15 Changed 7 years ago by trac-o-bot

Resolution: invalid
Status: pendingclosed

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!

Note: See TracTickets for help on using tickets.