viztracer · Issues· 33 open
Open on GitHubLocally synced open issues (discussions stay on GitHub)
- #673
`vizviewer` parses the entire trace file just to read `file_info`
Updated Sep 17, 2026 - #693
vizviewer: Source code cannot be found on Windows
Updated Sep 17, 2026 - #685
When stack_depth=0, log_sparse does not respond to the tracer's log_func_args and log_func_retval parameters
Updated Sep 17, 2026 - #692
Feature Request: Add documentation for the report JSON structure
Updated Sep 1, 2026 - #682
[BUG] Yocto on aarch64, LICENSE and attach_linux_amd64.so
Updated Aug 25, 2026 - #687
snaptrace_threaddestructor calls PyGILState_Ensure() after interpreter finalization, causing SIGSEGV
Updated Aug 13, 2026 - #669
Feature Request: Support Perfetto Protobuf Input
Updated May 20, 2026 - #670
Feature Request: Return mock object from `get_tracer()` when inactive
Updated Feb 5, 2026 - #632
VizTracer --log_torch triggers an error and segfault on exit when used in conjunction with PyTorch profiler and the multiprocessing mode of DataLoader, where kineto_results is None.
Updated Nov 2, 2025 - #609
Doesn't appear to trace into multiprocessing.Process()
Updated Jul 17, 2025 - #604
TLS should be updated when the syscall fork is invoked
Updated May 24, 2025 - #594
Enhance viztracer's process attachment capability
Updated May 14, 2025 - #583
Viztracer + torch.compile never exits
Updated May 9, 2025 - #574
absolute include file not working.
need reproUpdated May 9, 2025 - #582
Segmentation fault
need reproUpdated May 9, 2025