Re: process crash
peter <p2.edoc-gM/[email protected]>
| Newsgroups | gmane.lisp.mcl.general |
|---|---|
| Message-ID | <p06240800c68c6fa11f8d@[192.168.1.44]> |
At 5:15 PM -0700 09/7/21, Terje Norderhaug wrote: >[...] >**** File :rmcl:level-1:l1-processes.lisp, After "(defppclapfunction >get-tick-count ()" >< (check-nargs 0) >< (mflr loc-pc) Why do we have to check the args (ask I while demonstrating my LAP ignorance)? Commenting out (check-nargs 0) hasn't made any effect that I can see yet. Re. process-preset, your demo code does not crash for me Terje. Nor does (process-run-function "Seldom Starts" (lambda ()())) Ron. Though that does seem to highlight inefficiencies (presumably Rosetta): (LOOP REPEAT 100 DO (PROCESS-RUN-FUNCTION "Seldom Starts" (LAMBDA NIL NIL)) (SLEEP 0.1)) took 25.583 seconds to run. Of that, 25.109 seconds were spent in The Cooperative Multitasking Experience. (which seems high - CLZ (Clozure) takes 10.6 seconds). (loop repeat 1000 do (PROCESS-RUN-FUNCTION "Seldom Starts" (LAMBDA NIL NIL))) did hang. Will experiment to try to discover what I can get to make it crash consistently. Anyway, suggestion: that we detail with our posts the context in which we're doing anything on RMCL. Here I'm running vanilla RMCL with rmcl-clos-patch on MacOS 10.5.7 on MacPro. _______________________________________________ info-mcl mailing list [email protected] http://clozure.com/mailman/listinfo/info-mcl