Shivam Raikundalia 9ffcca7060 [Profiler] Handle Tensor Sizes/Strides Parsing Error (#134862) ... Summary: Currently some jobs are encountering the following trace, P1539415198. This suggests that when we are parsing through tensors the path is prone to encountering an invalid address. This is is possibly occurring because for some reason the sizes() and strides() of a Tensor seem to not be of the same dimensions. We assume such when iterating through the shapes to get the Ivalue generator. When browsing some of the tensor implementations, I found that some of the size and stride paths are different which could be the cause of this issue. Regardless, the profiler should be flexible enough to handle such issues without bringing down the whole main thread. If the crashes still persist, it will still give us a data point as to where they are occurring and we can rule out the strides/sizes as the culprit Test Plan: This change doesn't break anything in the happy path, just makes sure the bad path is not exited abruptly. We should use this in order to debug what the events are having mismatching dimensions between sizes and strides. Differential Revision: D62008788 Pull Request resolved: https://github.com/pytorch/pytorch/pull/134862 Approved by: https://github.com/aaronenyeshi		2024-09-03 23:46:38 +00:00
..
combined_traceback.cpp
combined_traceback.h
init.cpp	[Profiler] Handle Tensor Sizes/Strides Parsing Error (#134862)	2024-09-03 23:46:38 +00:00
init.h
pybind.h