primoze
primoze
DDeno
Created by primoze on 11/16/2023 in #help
Segfault when creating second rust MainWorker in program
Hello. Not sure if this is the place to ask since it seems to be a v8 issue (or perhaps an issue with the bindings), but I figured at least people here can point me in the right direction. I have a segfault issue after updating deno_runtime from 0.122.0 to 0.131.0 (deno_core 0.199.0 to 0.229.0). My program segfaults when starting a second worker after the first one has completed, and on a different thread. Running in valgrind it doesn't crash, but it does print a few ==419765== Warning: set address range perms: large range [0x120f7000, 0x32136000) (noaccess), but as far as I can figure out this is just a log for valgrind developers. Using gdb with a core dump I narrowed down the issue to v8::internal::Heap::SetUpSpaces(v8::internal::LinearAllocationArea&, v8::internal::LinearAllocationArea&), but I'm wondering if I'm doing something wrong to be hitting this issue, or if someone else has encountered this. IIRC the last few versions of deno_core have the same v8 version (0.81.0), so it seems strange that nobody encountered this before if I'm doing everything right. I have a minimal reproducible example here: https://github.com/primoze/set-up-spaces I haven't found anything regarding SetUpSpaces searching online, so I thought I'd ask here.
14 replies
DDeno
Created by primoze on 11/22/2022 in #help
deno_runtime inspector service not starting...
Hi! I'm embedding deno_runtime, and I can't get the inspector working. I set BootstrapOptions.inspect to true, and WorkerOptions maybe_inspector_server and should_break_on_first_statement. The server is set to listen on 127.0.0.1:9229. server in inspector_server.rs is called, and prints
Debugger listening on ws://127.0.0.1:9229/ws/5b5725e4-ac19-4f4d-ba1b-f6d44ce9430f
Visit chrome://inspect to connect to the debugger.
Deno is waiting for debugger to connect.
Debugger listening on ws://127.0.0.1:9229/ws/5b5725e4-ac19-4f4d-ba1b-f6d44ce9430f
Visit chrome://inspect to connect to the debugger.
Deno is waiting for debugger to connect.
but make_svc function is never called (I added some printlins), and netstat shows the port is not in use, and chrome doesn't find it either. Permissions are allow all, cert errors are ignored, I can post the entire setup if required... Everything is created and running inside run_local, and the versions are 0.160.0 and 0.86.0 for core and runtime respectively (but a few older versions also didn't work). What am I missing? Are there any other options relevant to starting the inspector service?
12 replies