memory leak
17 views
Skip to first unread message
Pouyan Ziafati
Nov 25, 2014, 10:31:05 AM11/25/14
to eta...@googlegroups.com
Dear Paul, dear Darko,
There is a memory leak in etalis.
To reproduce, add the following rule to the etalis Prolog code and call "make_it(1)".
make_it(X):-
event(hi('hello')),make_it(X).
Memory grows unbounded. Any idea?
Many thanks,
Pouyan
There is a memory leak in etalis.
To reproduce, add the following rule to the etalis Prolog code and call "make_it(1)".
make_it(X):-
event(hi('hello')),make_it(X).
Memory grows unbounded. Any idea?
Many thanks,
Pouyan
Pouyan Ziafati
Nov 25, 2014, 12:39:07 PM11/25/14
to eta...@googlegroups.com
Obviously the rule in my previous email eats all memory, sorry for that.
Nevertheless, in the executor.P file, in "event_trigger(event(Event,[T1,T2])):- ..." rules, there are "assert(fired_event(Event,[T1,T2]))" clauses which were the cause of memory growing unbounded.
Cheers,Nevertheless, in the executor.P file, in "event_trigger(event(Event,[T1,T2])):- ..." rules, there are "assert(fired_event(Event,[T1,T2]))" clauses which were the cause of memory growing unbounded.
--
You received this message because you are subscribed to the Google Groups "ETALIS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to etalis+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Pouyan Ziafati
PhD candidate,
University of Luxembourg (SnT) / Utrecht University (Intelligent Systems Group)
Mobile: +352-661661881
PhD candidate,
University of Luxembourg (SnT) / Utrecht University (Intelligent Systems Group)
Mobile: +352-661661881
Reply all
Reply to author
Forward
0 new messages