Bug #2352
Mis à jour par Serge Heiden il y a plus de 7 ans
Currently, reloading a X CQP corpus in the current session (search engine restart) can lead to a "X corpus not ready" status whereas the X corpus could be correct (on disk).
h3. Solution
* after X import or load, check the X corpus status: if the status is not ready ->
## # drop each CQP corpus (to free as much of C heap memory as possible)
## # unload cqplib (to free remaining memory pointers - typically in C stack memory - but assuming possible memory leaks)
## # load cqplib
## # load each CQP corpus
*** ** check the X corpus status: if the status is not ready -> invite to quit TXM and relaunch it (see #2351)
h3. Solution
* after X import or load, check the X corpus status: if the status is not ready ->
## # drop each CQP corpus (to free as much of C heap memory as possible)
## # unload cqplib (to free remaining memory pointers - typically in C stack memory - but assuming possible memory leaks)
## # load cqplib
## # load each CQP corpus
*** ** check the X corpus status: if the status is not ready -> invite to quit TXM and relaunch it (see #2351)