Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Launch implementation: RangeError: Maximum call stack size exceeded

Avatar

Avatar
Validate 1
Level 2
sebastiane27965
Level 2

Likes

8 likes

Total Posts

40 posts

Correct Reply

3 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
Affirm 3
View profile

Avatar
Validate 1
Level 2
sebastiane27965
Level 2

Likes

8 likes

Total Posts

40 posts

Correct Reply

3 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
Affirm 3
View profile
sebastiane27965
Level 2

03-04-2020

Hi, have run into a problem with our launch implementation without being able to pinpoint the source of this error, maybe someone has any input here:

It starts of with this error: RangeError: Maximum call stack size exceeded

And then 10000 lines of this:

at u (VM35 launch-88-development.min.js:formatted:2902)
at d.x.fetchPermissions (VM35 launch-88-development.min.js:formatted:1403)
at Ne.m.init (VM35 launch-88-development.min.js:formatted:3781)


the particular lines of code it points to are:

return f.optIn.fetchPermissions(u, !0);

 

And:

 

return !i || i && x.isComplete || c ? e(x.permissions) : a || j.add(Ie, function() {
return e(x.permissions)

 

after going through this cycle once the error seems to go away, so i assume it is trying to do something on something that is not yet available to fetch the value of, any suggestion on what to try here? All help greatly appreciated 🙂

 

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 1
Level 2
sebastiane27965
Level 2

Likes

8 likes

Total Posts

40 posts

Correct Reply

3 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
Affirm 3
View profile

Avatar
Validate 1
Level 2
sebastiane27965
Level 2

Likes

8 likes

Total Posts

40 posts

Correct Reply

3 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
Affirm 3
View profile
sebastiane27965
Level 2

08-04-2020

Hi, for anyone running into a similar error, this was actually caused by the fact that Adobe Target was running an old version of at.js (1.8.0), causing the analytics call to be disrupted by a slow Target request, an update of at.js to 2.3.0 solved this. 

Answers (1)

Answers (1)

Avatar

Avatar
Shape 25
MVP
Andrey_Osadchuk
MVP

Likes

536 likes

Total Posts

968 posts

Correct Reply

263 solutions
Top badges earned
Shape 25
Bedrock
Coach
Boost 500
Affirm 250
View profile

Avatar
Shape 25
MVP
Andrey_Osadchuk
MVP

Likes

536 likes

Total Posts

968 posts

Correct Reply

263 solutions
Top badges earned
Shape 25
Bedrock
Coach
Boost 500
Affirm 250
View profile
Andrey_Osadchuk
MVP

05-04-2020

I presume you added a custom JS code with a function that calls itself that makes an infinite loop. Review the code.