Custom Query (1030 matches)

When using a trunk darwinx8664 lisp at r15433 on Mountain Lion, slime often takes tens of seconds to start up.

At a quick first glance, I observe that allocate_tcr() often ends up looping hundreds of thousands, or even millions, of times before it gets a TCR that has a suitable address to use as a Mach port name.

Slime creates several threads at a startup, and usually a few of them end up taking a while to get going. Crudely instrumenting allocate_tcr() shows that the time to find a suitable port name can take anywhere from under a second to 20 seconds or more.

From r15343, perhaps?

ChromeKote:ccl svspire$ ./dx86cl64 -n Welcome to Clozure Common Lisp Version 1.8-r15290M (DarwinX8664)! ? (set-syntax-from-char #\u+feff #\space) T ?

ChromeKote:ccl svspire$ ./dx86cl64 -n Welcome to Clozure Common Lisp Version 1.9-dev-r15382M-trunk (DarwinX8664)! ? (set-syntax-from-char #\u+feff #\space)

Error: Array index 254 out of bounds for #<SIMPLE-VECTOR 1> . While executing: (SETF CCL::SPARSE-VECTOR-REF), in process listener(1). Type :POP to abort, :R for a list of available restarts. Type :? for other options.

1 >

the function initGlut() must be called with a pointer to a variable containing argc and a pointer to argv. Instead, it is being called with a pointer to a pointer to argv (line 45 in examples/opengl-ffi.lisp). Simplest fix is to remove the creation and initialization of argvp, and to change line 45 to read (#_glutInit argcp argv)))

Cheers, Hans-Martin