Crash when trying to use profiling from debugger

Community Usage questions
1

Hi

I am currently migrating a complex dashboard to v1.

When starting, my app sends some OSC to o-s-c, and o-s-c freezes for 20 to 30 seconds.

In v0, it could freeze 2 or 3 sec max.

I tried to use the ‘performance’ tab of the chrome debugger, but it crashes the whole application.

This is on arch linux.

I get this printed in the terminal:

[1269243:1110/144440.787380:ERROR:CONSOLE(24)] "Empty response arrived for script 'devtools://devtools/remote/serve_file/@8342c2e9766731779b0dd0419f9524b2cfae5ffb/product_registry_impl/product_registry_impl_module.js'", source: devtools://devtools/bundled/shell.js (24)
[1269243:1110/144440.793589:ERROR:CONSOLE(109)] "Uncaught (in promise) Error: Could not instantiate: ProductRegistryImpl.Registry", source: devtools://devtools/bundled/shell.js (109)
[1269243:1110/144440.793649:ERROR:CONSOLE(109)] "Uncaught (in promise) Error: Could not instantiate: ProductRegistryImpl.Registry", source: devtools://devtools/bundled/shell.js (109)
[1269243:1110/144440.793703:ERROR:CONSOLE(109)] "Uncaught (in promise) Error: Could not instantiate: ProductRegistryImpl.Registry", source: devtools://devtools/bundled/shell.js (109)
tracing_service_impl.cc: Configured tracing, #sources:2, duration:0 ms, #buffers:1, total buffer size:102400 KB, total sessions:1
tracing_service_impl.cc: Tracing session 1 ended, total sessions:0
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0230

After that, o-s-c and the debugger stay both do not react to anything anymore.

but received OSC messages are still printed to the terminal (in debug mode)

I can try to share a minimum repro dashboard and example, but would such a performance recording be useful?

Thx

2

Sorry but I won’t be able to do anything regarding the debugger, it’s not something I have the hands on. It (the debugger) may work better using an external browser instead of the default client gui.
Once more, I don’t think migrating a very heavy and complex session is a good idea, tracking each change sounds just too big a task…

3

you think I should rather restart my session from scratch in v1 @jean-emmanuel ?

4

Well yes unless sticking with v0 does the job :slight_smile:

5

It does for now but there are new features in v1 that could be useful and bring better perf.

And nothing guarantees that I’ll still be able to build o-s-c v0 in a few month, as we’ve seen recently ;-(

6

Just in case, can you upload your session ?

7

here it is, still in v0 format.
incoming…
tod_djj_multi.json (360.2 KB)

8

I see there are logs of messages i the console due to the migration or to incorrect properties, I can try to fix them

9

Ok honestly I would stick to v0 for this session, you’re going to have a long and frustrating time otherwise. There are many prebuilt binaries for v0, you can back them up if needed.