P01-1044 |
implemented in Java , which uses
|
garbage collection
|
for memory management . Even
|
H89-1045 |
needed for each sentence without
|
garbage collection
|
. Note that the memory savings
|
H89-1045 |
parsing framework : pruning ,
|
garbage collection
|
, training . The chart parser
|
H89-1045 |
Table 4 summarizes the effect of
|
garbage collection
|
on space requirements for the
|
J00-1005 |
engine , nor the time required for
|
garbage collection
|
. In order to establish that
|
H89-1045 |
we have embedded a time-stamp
|
garbage collection
|
scheme into the chart parser
|
N10-1014 |
is helpful for avoiding the "
|
garbage collection
|
" ( Moore , 2004 ) problem for
|
J03-1003 |
background activities such as
|
garbage collection
|
. Table 1 shows that even for
|
A00-3002 |
Care was taken to disable lisp
|
garbage collection
|
during parsing . As it was expected
|
D13-1112 |
align - ments , alleviating the
|
garbage collection
|
problem . We use the SRILM toolkit
|
D15-1209 |
technique on the example . The
|
garbage collection
|
has not occurred , and the alignment
|
C96-1019 |
generation timings do not include
|
garbage collection
|
time . The grammar used for the
|
H89-1045 |
invaluable insight on pruning and
|
garbage collection
|
, for sharing his expertise on
|
H89-1045 |
have further shown that pruning ,
|
garbage collection
|
, and training algorithms may
|
C88-1012 |
, for instance , asynchronous
|
garbage collection
|
in Lisp ) , the intrusion of
|
C00-2152 |
we found that l ) el ' - rule
|
garbage collection
|
reduced the overall read/write
|
E97-1060 |
background of the implementation of a
|
garbage collection
|
procedure which projects variables
|
P01-1044 |
primary data struc - tures , "
|
garbage collection
|
thrashing " can occur when logical
|
H05-1036 |
collection . In our experiment ,
|
garbage collection
|
was called explicitly after each
|
M95-1007 |
high and we risked a crash due to
|
garbage collection
|
being unable to reclaim enough
|