[Glass] [GLASS] Seaside - growing extent - normal?

[Lawrence Kellogg via Glass]

LOL. We fought a long and hard battle, and I'm not sure of the outcome, except that my extent is still big, and I just got a another paying gig. 

Some day, I'll take another shot at it.

Best,

Larry



> On Jul 5, 2015, at 4:45 AM, Mariano Martinez Peck <marianopeck at gmail.com> wrote:
> 
> Hi guys, 
> 
> I think I might have a similar issue as Lawrence. But it's hard to debug 58 messages ;)
> I thought this: https://github.com/GsDevKit/Seaside31/issues/68
> Should I start by trying this and see if there is a difference? 
> If not, anyway of the involves could have a little executive summary :) hahahahah Now..for real..this is just a heads up saying I may have the same problem and hence more hands to try and find this bug (if it is so)!
> 
> Cheers,
> 
>> On Wed, Apr 8, 2015 at 11:51 PM, Dale Henrichs via Glass <glass at lists.gemtalksystems.com> wrote:
>> 
>> 
>>> On 4/8/15 6:49 PM, Lawrence Kellogg wrote:
>>> 
>>>> On Apr 8, 2015, at 12:53 PM, Dale Henrichs <dale.henrichs at gemtalksystems.com> wrote:
>>>> 
>>>> Yes.
>>> 
>>> I’ve run it a number of times today but keep running out of temporary object memory
>> Hmmmmmm,
>> 
>> Running out of TOC is not a good thing ... running out of TOC and not recording a stack (like I needed the last time this happened) is not a good thing ... Without a stack I don't know where you blew out ... without a complete stack I don't know whether or not you are making any progress at all....
>> 
>> I am also suspicious that running out of memory is the source of some of the object leaks ...
>> 
>> I was under the impression that before making and restoring from backup that you had made a "complete" run without running out of TOC. Am I remembering wrong?
>> 
>> Today have you had any runs without running out of TOC ... I thought you had made it through one run today without running out of TOC. Am I remembering wrong?
>> 
>> I just need a full stack from your last run and we'll see what's happening ... remember the instructions from last time? The gem log should have some stacks that I can look at (pick the last stack in the file) and see if I can figure out what the heck is going on ...
>> 
>> Maybe, just maybe we are blowing out of memory because we've gotten to a spot that's never been executed before?
>> 
>> Dale
>> 
>> 
>> 
>> _______________________________________________
>> Glass mailing list
>> Glass at lists.gemtalksystems.com
>> http://lists.gemtalksystems.com/mailman/listinfo/glass
> 
> 
> 
> -- 
> Mariano
> http://marianopeck.wordpress.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20150705/198741da/attachment.html>