IRC channel logs

2021-12-22.log

back to list of logs

<fnstudio_>hey, i've tried to build a 500x500x500 array and all seems to be fine; if i try with a 1000**3 array though, that will fail - it says "killed"
<fnstudio_>of course, i imagine i'm allocating too much mem
<fnstudio_>i was curious to know where the "bottleneck" (or "safeguard mechanism") is
<fnstudio_>e.g. built-in as a constraint in the Guile interpreter or rather at the OS level or something else?
<tohoyn>daviid: gtk-css-provider-load-from-data doesn't work. do you want a snippet?
***nckx is now known as nckxmas
<daviid>tohoyn: yes
<tohoyn>daviid: I'll make the snippet later today
<tohoyn>daviid: here: https://paste.debian.net/1224446/
<tohoyn>daviid: here is the output I get: https://paste.debian.net/1224448/
<taylan>fnstudio_: if the guile process just abruptly ends with the message "killed" then I think that's the OS killing it
<taylan>fnstudio_: guile itself has a mechanism for calling a function in a context with limited stack memory but I'm not sure if this will help with creating an array directly on the heap: https://www.gnu.org/software/guile/docs/docs-2.2/guile-ref/Stack-Overflow.html
<taylan>fnstudio_: ah, there's also call-with-allocation-limit: https://www.gnu.org/software/guile/manual/html_node/Sandboxed-Evaluation.html
<rlb>I'm trying to figure out what a guile dialect should do wrt autocompilation -- i.e. how does it know whether or not it should autocompile (assuming it's trying to respect guile's normal behavior there)? (Also not sure I fully understand what I'm doing there yet...)
<rlb>Hey, seems like maybe your git server's having trouble (didn't know if you knew):
<rlb> $ git fetch johill
<rlb> fatal: unable to access 'https://git.sipsolutions.net/bup.git/': The requested URL returned error: 502
<rlb>
<rlb>oops - wrong channel
<rlb>...wrt compilation, right now what I do is just call compile-file with (compiled-file-name) once I determine that we need to (this is for indirectly "required" modules), but that's perhaps wrong if auto-compilation is disabled via the envt, cmdline, etc.
<fnstudio_>taylan: oh very interesting, thanks!
<fnstudio_>i'll experiment with the stack overflow mechanism then, thanks
<pinoaffe>daviid: thanks for the info! I'll try and see which one of em fits my needs best