Viztracer

Latest version: v1.0.1

Safety actively analyzes 701533 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 12 of 15

0.4.2

Underlying C structure for the module is changed. Most global variables are moved to objects, which means each VizTracer object actually has their own set of data.

We support module run now with viztracer -m module

trace_and_save is added to periodically save trace in a long program

--log_return_value is supported

some fixes on fork_save

0.4.1

Fix flamegraph, it's been not working for a while and I did not realize it.

Fix important command line bugs, where "__name__" is not __main__. Also not even the script run exit() in their code, they will have trace.

Added secret feature fork_save, has not documented it yet. That's prepared for the next "profile as you run" feaature

0.4.0

0.4.0 is the same as 0.3.4, We boosted the minor version for Windows support.

0.3.4

We now support Windows! viztracer can be directly called through console command viztracer your_script.py

0.3.3

VizTracer now supports gz file, which could save disk space significantly while still being compatible with Chrome.

Several optimizations were applied

* include/exclude files overhead is reduced by not using realpath
* with orjson, json can be directly dumped without decoding and encoding again
* class name is not read anymore
* thread id now makes more sense on both linux and mac

0.3.2

Unified the customized event VizCounter and VizObject. Now they have similar interface and it's easier to use them. Also fixed a source tar error that the header file is not included in the .tar file.

Page 12 of 15

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.