Custom Query (1030 matches)
Results (205 - 207 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #379 | fixed | results of HEAP-UTILIZATION on x8632 are fishy | ||
| Description |
Welcome to Clozure Common Lisp Version 1.3-dev-r11353M-trunk (DarwinX8632)! ? (heap-utilization) Object type Count Total Size in Bytes CONS 126038 1008304 BOGUS 3 0 BIGNUM 149 1156 SHORT-FLOAT 24 96 DOUBLE-FLOAT 12 144 COMPLEX 1 8 MACPTR 139 2636 FUNCTION 12138 5348712 BASIC-STREAM 34 22355952 SYMBOL 34835 975380 XCODE-VECTOR 1 0 LOCK 120 2880 HASH-TABLE-VECTOR 72 324848 POOL 23 92 POPULATION 22 268 PACKAGE 15 480 SLOT-VECTOR 4628 199512 STANDARD-INSTANCE 4183 50196 STRUCTURE 3283 123116 INTERNAL-STRUCTURE 2587 67232 VALUE-CELL 19 76 SIMPLE-VECTOR 23960 1089208 SIMPLE-UNSIGNED-LONG-VECTOR 1 4092 SIMPLE-BASE-STRING 7683 473928 SIMPLE-BIT-VECTOR 1 2097152 Those BASIC-STREAM objects are pretty heavyweight...not to mention the presence of BOGUS and XCODE-VECTOR objects that take up no space. |
|||
| #381 | fixed | hang when displaying NSRect record | ||
| Description |
Start IDE with (require 'cocoa). (Either 64- or 32-bit x86). Into a listener, type: (defvar *junk* (ns:make-ns-rect 0 0 100 100)) *junk* The IDE will hang. |
|||
| #382 | fixed | write-string / write-simple-string error | ||
| Description |
? (funcall #'(lambda () (write-string "foobar" t :end 2))) > Error: value NIL is not of the expected type UNSIGNED-BYTE. > While executing: (:INTERNAL BAD-SEQUENCE-INTERVAL CHECK-SEQUENCE-BOUNDS), in process listener(1). > Type :POP to abort, :R for a list of available restarts. > Type :? for other options. 1 > :b (6A5978) : 0 (FUNCALL #'#<(:INTERNAL BAD-SEQUENCE-INTERVAL CHECK-SEQUENCE-BOUNDS)> "foobar" NIL 2) 181 (6A59A8) : 1 (FUNCALL #'#<#<STANDARD-KERNEL-METHOD STREAM-WRITE-STRING (BASIC-CHARACTER-OUTPUT-STREAM T)>> #<BASIC-CHARACTER-OUTPUT-STREAM ISO-8859-1 (TTY/1) #x300040EF978D> "foobar" NIL T) 669 (6A5A40) : 2 (WRITE-SIMPLE-STRING "foobar" T NIL 2) 1637 We see that WRITE-SIMPLE-STRING is getting NIL as the START parameter. I'm not sure if the problem here is with the compiler macro on WRITE-STRING, or with WRITE-SIMPLE-STRING. We could change the compiler macro to provide a default value of 0 for the start keyword argument, or else we could change the WRITE-SIMPLE-STRING deal with a possibly NIL value for START in the case where the stream isn't a basic-stream, e.g., by writing (or start 0) in the call to STREAM-WRITE-STRING. (I'd just go ahead and change the compiler macro, but i assume that WRITE-SIMPLE-STRING is a performance hack, and I don't want to mess that up.) |
|||
