Skip to content

create coredump with running in inspect #41178

Open
@alvin-7

Description

@alvin-7

Version

14.18.2

Platform

Linux n248-141-178 4.19.117.bsk.6-amd64 #4.19.117.bsk.6 SMP Debian 4.19.117.bsk.6 Mon Jan 4 07:25:51 UTC x86_64 GNU/Linux

Subsystem

No response

What steps will reproduce the bug?

create coredump with running in inspect

How often does it reproduce? Is there a required condition?

Appear at random times
Suspect something node run with Inspect

What is the expected behavior?

node progress running normal

What do you see instead?

(llnode) bt
thread #1, name = 'node', stop reason = signal SIGSEGV
frame #0: 0x00007fe1fe74d305 libc.so.6___lldb_unnamed_symbol994$$libc.so.6 + 741 frame #1: 0x00007ffc46bd55c5 nodenode::inspector::(anonymous namespace)::WsHandler::OnData(std::vector<char, std::allocator >*) + 645
frame #2: nodeuv__read(stream=<unavailable>) at stream.c:1239 frame #3: nodeuv__stream_io(loop=, w=, events=) at stream.c:1306
frame #4: nodeuv__io_poll at linux-core.c:462 frame #5: nodeuv_run(loop=, mode=) at core.c:385
frame #6: 0x00007ffc46bc975e nodenode::inspector::InspectorIo::ThreadMain() + 1662 frame #7: 0x00007fe1fe9ca4a4 libpthread.so.0start_thread + 196
frame #8: 0x00007fe1fe70cd0f libc.so.6`clone + 63

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    inspectorIssues and PRs related to the V8 inspector protocol

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions