Pascal Mütschard
Pascal Mütschard
can you please include the stacktrace shown in the details of the error dialog, or the log?
Thanks for the stack trace. Yes, it would be nice to automatically include it, however, GH is very limiting in that it has to be a HTTP GET request, which...
Interesting. I just looked at the given trace and it open really fast using with very little memory usage. I also tried it with an OpenJDK 11, but I don't...
Also, could you please note witch process is actually pegged at 100%? is it a java process or is it `gapis`?
After launching GAPID, please run `killall -3 java`, which will cause the JVM to dump to stdout the stack trace of every thread. Please post the output here. Thanks.
Something to try, to see if not forcing GTK2 would unblock you. Try running the UI directly (i.e. not through the `gapid` launcher): ``` java -jar /lib/gapic.jar --gapid ```
This appears to not be fixed quite yet. Here is another stack trace form a different machine: ``` #0 0x00007faeb48d2bbe in xcb_send_request_with_fds64 () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #1 0x00007faeb48d3129 in xcb_send_request ()...
The trace was taken with: `../bazel-bin/pkg/gapit trace -capture-frames 3 -api vulkan /usr/bin/vulkan-smoketest` The crash happens with ` ../bazel-bin/pkg/gapit screenshot vulkan-smoketest.gfxtrace` The trace and replay were done on the same machine....
Note the above crash also happens with DCE off.
It fixed most cases, however, the RenderPass group still is broken: The node at [1, 0, 7, 0, 0, 0] (RenderPass) is for commands [0]-[6]- Should be [371, 0, 0]