gui/gui-test/tests/gracket
..
.gitignore
button-steps.txt
cache-image-snip-test.rktl
cache-image8.mre
canvas-steps.txt
checkbox-steps.txt
choice-list-steps.txt
combo-steps.txt
draw-info.txt
draw-mem.rkt
editor.rktl
flush-stress.rkt
frame-steps.txt
gauge-steps.txt
gc-blits.rkt
gl-bitmap.rkt
gl-refresh.rkt
image-snip-unmarshalling.rkt
info.rkt
item.rkt
load-handler.rkt
loadtest.rktl
media3.mre
media6.mre
media8.mre
mediastream.example
mem.rkt
menu-steps.txt
nruter.xbm
paramz.rktl
pasteboard.rkt
prog6.mre
prog8.mre
racket-ns.rkt
radiobox-steps.txt
README
sandbox-gui.rkt
scheme-ns.rkt
showkey.rkt
slider-steps.txt
test-editor-admin.rkt
test.rkt
testbox6.mre
testbox8.mre
testing.rktl
undo.rkt
unflushed-circle.rkt
windowing.rktl
wxme-load.rkt
wxme-random.rkt
wxme.rkt

The "item.rkt" test (use `require') creates a frame to select among
several types of control-testing frames. Click the `Get Instructions'
button in the top-left for more information.

---------------------------------------------------------------------------

The "mem.rkt" test
  gracket mem.rkt
creates a lot of frames and instance of other objects, reporting
memory information along the way. At the end, before the last memory
dump, objects that are still allocated are displayed like this:
  (frame (1 . 5))
This means that the frame allocated by thread #1 at cycle 5
(counting down from some number) hasn't been garbage-collected.
If there's a few of these lines (around 10), that's ok.
A large number of lines (say, 50) indicates a GC problem.