**** BEGIN LOGGING AT Thu Apr 04 02:59:58 2013 Apr 04 03:16:43 has anyone had a "maximum call stack exceeded" error? Apr 04 03:24:55 how many callbacks did you set? Apr 04 03:25:30 depends on what you mean? Apr 04 03:26:17 there's some relatively complex data passing happening Apr 04 03:26:22 through a series of bubbles Apr 04 03:26:33 but it worked prior to the most recent git pull Apr 04 03:29:02 although I've been testing using debug.html Apr 04 03:29:07 not index.html Apr 04 03:31:48 or at least some complex interactions happening Apr 04 03:34:18 I'm tracking where the classtack gets angry right now Apr 04 03:42:07 it's in a for loop that get's called after a createComponent() finishes the create(), first time through Apr 04 03:42:54 passing data as a published attribute to the component, so we can parse it, and build out a form (with some special components) dynamically Apr 04 03:57:12 is there a maximum data size that can be stored in memory in a deployed application? Apr 04 04:35:52 I don't think there is a limit for the javascript heap size that I know of, so it would be what ever the overhead of the browser is and the executing js code and the amount of ram on your pc Apr 04 04:36:55 I know I have seen some javascript heaps get into the gigs because of poor cleanup Apr 04 04:39:28 I'm wondering if enyo sets one Apr 04 04:40:07 I don't think there is a way inside the javascript runtime to set a heap size Apr 04 04:40:22 I know if googles v8 there is a way to set the call stack size Apr 04 04:40:37 but that has to be done before the runtime is running Apr 04 06:45:32 so, it's coming from a call-chain that originates from enyo.Signals.Send(). I assume this is why (as I assume the event chain gets it's own stack, and stays there until all sub-functions finish) Apr 04 06:45:41 I have no idea, however, how to get around this Apr 04 13:15:01 summatusmentis: a good bet may be to figure out how to get the big data objects on the heap, instead of on the call-stack. i don't know how you can control such thing in javascript. Apr 04 15:11:36 madnificent: they shouldn't be too big Apr 04 15:12:22 madnificent: I also switched them to localstorage, so most of them aren't being passed around Apr 04 15:12:28 this wasn't an issue at all in enyo 2.0 Apr 04 15:22:52 perhaps sugardave will know what's going on. i don't know the source by heart, especially not the source of the signals Apr 04 15:24:31 so, if I put the loop where the issue occurs into an anonymous function (assigned to a variable), it runs, but it loses the enyo context, I think Apr 04 15:48:36 summatusmentis: you can bind it and verify Apr 04 15:48:41 enyo.bind(this,function()....) Apr 04 15:53:41 yeah, if I bind it, I get the same error Apr 04 16:04:20 so it may be something else in your object that's keeping too much state (and is being placed on the stack). though i'm a tad surprised that the whole object is being placed on the stack. Apr 04 16:17:36 so, I'm doing some sort of hacky things creating trees of components, and referencing them in order to dynamically populate a view Apr 04 16:17:44 and my guess is that's part of the issue here Apr 04 16:59:00 I almost think I need to break some of this out into components Apr 04 20:43:30 Has anyone worked with the MVC in 2.2? I'm wondering if it is too late to move to that for my app Apr 04 20:43:36 Is it any good? Apr 05 01:50:49 what's up? **** ENDING LOGGING AT Fri Apr 05 02:59:58 2013