google/orbit

Can't capture with latest Orbit - Ubuntu

pierricgimmig opened this issue · 5 comments

Starting a capture stalls Orbit. This seem to be related to Improve module-lookup performance (#4716)

Using the previous commit works.

Might be related to invalid data in proto:

[2023-01-26T08:27:35.493400] [    ApiLoader/EnableInTraceeLinux.cpp:68] Enabling Api in tracee took 0.014 ms
[2023-01-26T08:27:35.493499] [         LinuxTracing/TracerImpl.cpp:104] No sample stack dump size was set; assigning to default: 65000
[2023-01-26T08:27:35.493527] [ProducerSideService/ProducerSideServiceImpl.cpp:28] About to send StartCaptureCommand to CaptureEventProducers (if any)
[2023-01-26T08:27:35.493561] [LinuxCaptureService/LinuxCaptureServiceBase.cpp:283] Starting memory watchdog with threshold 8372432896 B because total physical memory is 16744865792 B
[2023-01-26T08:27:35.493609] [         LinuxTracing/TracerImpl.cpp:753] Error: Could not read cpuset
[libprotobuf ERROR /home/pierric/.conan/data/protobuf/3.21.4/_/_/build/18f21867c020faed44015877339929f8659571fe/src/src/google/protobuf/wire_format_lite.cc:618] String field 'orbit_grpc_protos.CaptureStarted.executable_path' contains invalid UTF-8 data when serializing a protocol buffer. Use the 'bytes' type if you intend to send raw bytes. 

Uhhh. Interesting. We had to make some changes to code using u8strings so that it works in MSVC both in C++17 and C++20 mode.

Assigning to @florian-kuebler .

Thanks for reporting, @pierricgimmig . And sorry for breaking it.

Thanks for reporting, @pierricgimmig . And sorry for breaking it.

No worries, thanks for fixing @florian-kuebler and @beckerhe