compile fail on windows 10 about vk HOT 7 OPEN

Thanks for reporting. I'll look into it

from vk.

I tried to use cmd to load the package then i got this error. I think it should be sbcl‘s bug

here is the error log
C:\Users\admin>sbcl
This is SBCL 2.2.8, an implementation of ANSI Common Lisp.
More information about SBCL is available at http://www.sbcl.org/.

SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses. See the CREDITS and COPYING files in the
distribution for more information.

• (ql:quickload :vk)
  To load "vk":
  Load 1 ASDF system:
  vk
  ; Loading "vk"
  ..................................................
  ..................................................
  ..................................................
  ..................................................
  ..................................................
  ..................................................
  ............................................Heap exhausted during garbage collection: 32 bytes available, 112 requested.
  Immobile Object Counts
  Gen GF type fdefn symbol code Boxed Cons Raw Code SmMix Mixed LgRaw LgCode LgMix Waste% Alloc Trig Dirty GCs Mem-age
  2 0 0 0 0 0 12368 1951 2166 247 479 600 0 0 32 0.6 581217808 306949690 17843 1 1.2342
  3 0 0 0 0 0 9761 1674 1310 227 421 480 20 0 78 0.6 454850208 2000000 13971 0 0.0000
  4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0.0 0 2000000 0 0 0.0000
  5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0.0 0 2000000 0 0 0.0000
  fatal error encountered in SBCL pid 1696416064:
  GC invariant lost, file "gencgc.c", line 525

Welcome to LDB, a low-level debugger for the Lisp runtime environment.
(GC in progress, oldspace=2, newspace=3)
ldb>

from vk.

Yes, looks like sbcl ran out of memory during compilation. and when you try to load the systems later on, process-args is not defined because it's only available during compilation.
My last two weeks were a bit busy, sorry. I'll try to fix it this weekend.

from vk.

It doesn't matter, thanks. Maybe you could take a rest.

from vk.

I have the same problem on Debian. Is there a known workaround?

from vk.

As far as I know, this only happens during compilation, not at runtime.
So what you could try is to increase the dynamic space (sbcl --dynamic-space-size <MiB>) and/or lowering the debug compiler policy (using restrict-compiler-policy) when compiling vk and using your default settings afterwards.
I still need to figure out a permanent solution.

from vk.

Hi, has there been any update on this? Thanks!

from vk.