Re: Prolog, memory management and memory leaks

A.L. wrote:

1. I am using SICStus,
2. I have application written long ago, in SICStus 3.10.2. It is
embedded in J++ (Microsoft dialect of Java, now known as J#) using
in-process DLL that was implemented using SICStus Visual Basic
interface. This application runs in production environment, 7/24,
since 2004 without any problems
3. The application mentioned above was obsoleted and rewritten in Sun
Java and SICStus 3.12.8. Since the official interface to SICStus is
now Prolog Beans, I replaced JNI by Prolog Beans. However, the Prolog
code was not changed at all. This was as simple as adding a layer of
code that registers predicates for Prolog Beans.

This application crashes after about 50,000 calls to the server

4. New application was written; much larger and more complex, also
with Prolog Beans interface. This one crashes after 200 calls to the
server.

Have you tried looking at the output from statistics after 50 and after
a 100 calls to the server ?
This will at least uncover any growing "normal" Prolog execution stacks/heaps.

But maybe it is just a leak in the SICStus Prolog Beans which you need to make
SICS aware off, or once you can locate it, work around it ?

Cheers

Bart Demoen
.

Relevant Pages

  • Re: Prolog, memory management and memory leaks
    ... I have application written long ago, in SICStus 3.10.2. ... Java and SICStus 3.12.8. ... Since the official interface to SICStus is ... now Prolog Beans, I replaced JNI by Prolog Beans. ...
    (comp.lang.prolog)
  • Re: Prologs combined with other tools
    ... Recently I have found the pdf manual of SICSTUS Prolog. ... Yes, SICStus has several interfaces, including VisualBasic interface. ...
    (comp.lang.prolog)
  • Re: java calling prolog
    ... >SICSTUS Prolog provides an interface called JASPER which is just waht ... But then again SICSTUS is expensive, ... SICStus provides much better interface named PologBeans. ...
    (comp.lang.prolog)