Screenshot of "The Talos Principle" gfxtrace towards end of trace crashes
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 329
- PR merge metrics
- No merged PRs in 30d
Description
GAPID 1.1.0 on WIndows 10 64-bit (on Dell XPS 15 laptop w/ 16gb of RAM)
I captured a GfxTrace using GAPID of the Vulkan version of about 1 minute of gameplay in "The Talos Principle" that was about 3.1GB in size.
After the trace, If I dump out screenshots towards the end of my capture, then at some point the system starts bogging down, consuming all my resources (CPU, memory, and hard drive access), before it finally crashes. It seemed prior to the crash to be thrashing memory and performing a lot of memory paging prior to the crash.
In my case, I was trying to dump frame 3890 in my trace with the following command:
```
gapit screenshot -frame 3890 -out talos_trace_frame3890.png
```
and I got the following output:
```
2018/07/25 12:28:08 transport: http2Client.notifyError got notified that the client transport was broken read tcp 127.0.0.1:56139->127.0.0.1:56133: wsarecv: An existing connection was forcibly closed by the remote host..
18:28:08.065 E: rpc error: code = 13 desc = transport is closing
18:28:08.078 E: Main failed
Error: Get frame image data failed
Cause: rpc error: code = 13 desc = transport is closing
2018/07/25 12:28:08 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp: operation was canceled"; Reconnecting to {localhost:56133 }
2018/07/25 12:28:08 grpc: addrConn.transportMonitor exits due to: grpc: the connection is closing
```
Contributor guide
Assessment
This issue has not been assessed yet.