You were right: the problem was not caused by 11!:2999 but by an unintended growing of a return value in a myFunc&.> context. I have learned to appreciate i.0 as return value. Thank you very much for your reflection.
On Sun, Aug 8, 2010 at 3:29 PM, Eric Iverson <[email protected]> wrote: > I wonder if you are just seeing normal J memory allocation. That is, when > additional space is required for an array the size of the array is doubled > (memory allocation are in factors of 2). The 11!:2999 commands are added to > an internal buffer until they are flushed. I'm guessing you would observe > the same memory actions if instead of 11!:2999 you just did global=: > global,new_sutff > > > On Sun, Aug 8, 2010 at 7:39 AM, Jan Jacobs <[email protected]> wrote: > >> Eric, >> both Windows and 7!:0 show comparable memory consumption. >> I ran a smaller version of the GUI consisting of 600 "glrgb glbrush >> glrect" triples, followed by a few gllines, glellipse and gltext. >> 7!:0'' reveals an initial increase of 460K and then each glrect in >> this triple takes a moderate 384 bytes. However, the glrgb and glbrush >> double their claim occasionally (and hold on to it): >> after 20th triple --> 17K >> after 400th triple -> 33K >> after 800th triple -> 65K >> after 1600th triple -> 131K >> The thing that surprises me most is after the 600 triples (before the >> glrgb for the gllines) the memory claim is reduced significantly. >> I have not executed any 11!:2999 yet. My code uses also the $. >> facility but not for the GUI part. >> Why do these triples claim so much memory? >> Jan. >> >> On Fri, Aug 6, 2010 at 3:25 PM, Eric Iverson <[email protected]> >> wrote: >> > What does the J 7!:x show about space during this activity? If the space >> > problem shows up in windows task manager, and not in 7!:x then the >> problem >> > is in j.exe. There might be some workarounds for the problem. For >> example, >> > rather than repeatedly calling 11!:2999 (and perhaps triggering the >> > problem), build up to the final argument in J and then call 11!:2999 just >> 1 >> > time. >> > >> > On Fri, Aug 6, 2010 at 3:09 AM, Jan Jacobs <[email protected]> >> wrote: >> > >> >> ls, >> >> I'm experiencing an 'out of memory' problem when drawing a large GUI >> >> using gl2 (isigraph). A display list is built up gradually (in total >> >> approximately 200K entries/2MB) using the 11!:2999 facility. During >> >> the build the windows task manager reports a memory increase from >> >> 1.4GB to 4.8GB. The time for this build up is exceptionally long (4 >> >> minutes till the exception) while a slightly smaller version only >> >> takes 2 seconds to draw the GUI correctly. This smaller version also >> >> demonstrates that this huge memory claim is only temporary: when the >> >> GUI form is completely built up the claim is reduced to 1.4GB again. >> >> Questions are: what is claiming so much memory? In what directions can >> >> I look for solutions? I'm using a quad core i7 @2.8 GHz with 6 GB RAM. >> >> Thanks in advance, >> >> Jan. >> >> ---------------------------------------------------------------------- >> >> For information about J forums see http://www.jsoftware.com/forums.htm >> >> >> > ---------------------------------------------------------------------- >> > For information about J forums see http://www.jsoftware.com/forums.htm >> > >> >> >> >> -- >> Jan Jacobs >> Esdoornstraat 33 >> 5995AN Kessel >> W: www.sommaps.com >> T: +31 77 462 1887 >> M: +31 6 23 82 55 21 >> E: [email protected] >> ---------------------------------------------------------------------- >> For information about J forums see http://www.jsoftware.com/forums.htm >> > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > -- Jan Jacobs Esdoornstraat 33 5995AN Kessel W: www.sommaps.com T: +31 77 462 1887 M: +31 6 23 82 55 21 E: [email protected] ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
