keyboard interrupt #250
-
Does viztracer fail to create the result file if the software to be profiled is killed via keyboard interrupt ? I do not get any output in this case. Command I'm using: viztracer -o result.html script.py My workaround that worked was to break out of all the threads and exiting all processes after a certain time but it also includes too many changes in my code. Is there a way to profile the code using viztracer if the code is killed manually (keyboard interrupt or just kill -9 pid) after some time ? Thank you for your help |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 9 replies
-
It should save the result after keyboard interrupt. |
Beta Was this translation helpful? Give feedback.
-
Also another I had one more question. Is log_parse compatible with multiprocess ? |
Beta Was this translation helpful? Give feedback.
It should save the result after keyboard interrupt.
Can you share your code to profile and the os you are working on? Also python and viztracer version.