In a way, too many possible culprits mask each other.
I remember a problem like this that I solved by reducing the amount of
memory so the problem would show quickly, then testing small things in
isolation and volume. Pick a subset of tests and run them multiple times
at low memory until it fails or becomes clear it won't. Rinse and repeat.
On Sat, Aug 25, 2012 at 10:19 AM, Alexander J. Vondrak <
ajvond...@csupomona.edu> wrote:
> Okay, so still no luck:
>
> - Tried skipping tools.deploy tests (just yanked deploy-tests.factor out
> of
> the 0.95 source tree before `load-all test-all`), still crashed.
>
> - Tried skipping extra/ with `"resouce:core" load-root "resource:basis"
> load-root test-all`, still crashed.
>
> - Tried doubling the sizes of the GC generations (./factor -young=2
> -aging=4
> -tenured=1600) to no avail.
>
> - No particular vocabulary seems to be tripping it off, as verified by
> doing
> the above with
> ```
> \ run-test-file [
> [ dup "~/Desktop/tests" utf8 [ print ] with-file-appender ] prepend
> ] annotate
> ```
> and having them crash at different vocabs. The few times I managed to
> catch a glimpse of the factor process running in top, the memory usage
> just
> seemed to creep up to its ceiling as more and more tests were run
> until it
> finally aborted.
>
> It didn't use to do this (even very recently), which is what made me think
> it
> was something to do with my machine just being b0rked. I've had weird bugs
> crop up from time to time using Debian, so it's not unprecedented. I've
> been
> procrastinating setting up an Arch install on this machine, so maybe this
> is as
> good a reason as any to get around to that...
>
> Any other experiments I should try?
>
> Thanks for the help,
> --Alex Vondrak
>
> ________________________________________
> From: John Benediktsson [mrj...@gmail.com]
> Sent: Friday, August 24, 2012 6:54 PM
> To: factor-talk@lists.sourceforge.net
> Cc: factor-talk@lists.sourceforge.net
> Subject: Re: [Factor-talk] Out of memory error
>
> It might be worth only loading and testing vocabularies in core and basis,
> to see if GVN works?
>
> On Aug 24, 2012, at 6:50 PM, "Alexander J. Vondrak" <
> ajvond...@csupomona.edu> wrote:
>
> > It seems to fail soon after the tools.deploy tests. I tried at one
> point disabling those, but I think it still crashed. I should check
> again...
> >
> > ________________________________________
> > From: Doug Coleman [doug.cole...@gmail.com]
> > Sent: Friday, August 24, 2012 6:44 PM
> > To: factor-talk@lists.sourceforge.net
> > Subject: Re: [Factor-talk] Out of memory error
> >
> > 8gb outta be enough for anybody. But It's not, I guess. Try with more
> RAM or patch the part that grows to only grow to as much as you have.
> >
> > Maybe something is using waaaaay too much....
> >
> > On Aug 24, 2012 6:01 PM, "Alexander J. Vondrak" <ajvond...@csupomona.edu
> <mailto:ajvond...@csupomona.edu>> wrote:
> > Hey all,
> >
> > Mini-update: got the unit tests for the global value numbering pass more
> > up-to-snuff awhile ago (it's like test-driven development in reverse!).
> Still
> > seems like I should be doing more to test the new capabilities, but I'm
> not
> > sure if I could do much more than what's there.
> >
> > My efforts as of late have been focused on some GVN improvements. But
> for the
> > past way-too-long, I thought I had broken something catastrophic because
> > `load-all test-all` would invariably crash the listener with an "out of
> memory"
> > error:
> >
> > Out of memory
> >
> > Nursery: Start=831c0000, size=100000, end=832c0000
> > Aging: Start=82fc0000, size=200000, end=831c0000
> > Tenured: Start=50c80000, size=32140000, end=82dc0000
> > Cards:base=b44d0008, size=326800
> > Aborted
> >
> > After a lot of very slow debugging (them's the breaks when running all
> the unit
> > tests, I guess) that was ultimately fruitless, I finally tried out
> Factor 0.95
> > straight from the build farm---none of my changes, no .git, just a clean
> > download of the linux-x86-32 tarchive. And, what do you know, `load-all
> > test-all` still crashes with the same error.
> >
> > It hadn't done that before, so I think the issue may be an intervening OS
> > update I did. I'm running a fully up-to-date Debian testing, kernel
> > 3.2.0-3-686-pae.
> >
> > 1) Can anyone reproduce this error? Or is my machine just that jacked
> up? I'd
> > be happy to provide other diagnostic info, if it'd help.
> >
> > 2) Any coping mechanisms? I considered just throwing a bunch of memory
> at it
> > with command line switches (-young=, -aging=, -tenured=, etc.), but
> wasn't
> > really sure how much would do the trick, since it just started crashing
> like
> > this out of the blue anyway.
> >
> > Thanks,
> > --Alex Vondrak
> >
> ------------------------------------------------------------------------------
> > Live Security Virtual Conference
> > Exclusive live event will cover all the ways today's security and
> > threat landscape has changed and how IT managers can respond. Discussions
> > will include endpoint security, mobile security and the latest in malware
> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > _______________________________________________
> > Factor-talk mailing list
> > Factor-talk@lists.sourceforge.net<mailto:
> Factor-talk@lists.sourceforge.net>
> > https://lists.sourceforge.net/lists/listinfo/factor-talk
> >
> >
> ------------------------------------------------------------------------------
> > Live Security Virtual Conference
> > Exclusive live event will cover all the ways today's security and
> > threat landscape has changed and how IT managers can respond. Discussions
> > will include endpoint security, mobile security and the latest in malware
> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > _______________________________________________
> > Factor-talk mailing list
> > Factor-talk@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/factor-talk
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Factor-talk mailing list
> Factor-talk@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/factor-talk
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Factor-talk mailing list
> Factor-talk@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/factor-talk
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Factor-talk mailing list
Factor-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/factor-talk
