Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gapis crashes when loading a capture #2590

Closed
hevrard opened this issue Feb 7, 2019 · 6 comments
Closed

gapis crashes when loading a capture #2590

hevrard opened this issue Feb 7, 2019 · 6 comments

Comments

@hevrard
Copy link
Contributor

hevrard commented Feb 7, 2019

When opening a capture through the UI, gapis crashes, see log below.

$A0003

W20190207-103913000[server.ChildProcess$LoggingStringHandler][server.ChildProcess$LoggingStringHandler.lambda$new$0] gapis: terminate called after throwing an instance of 'spirv_cross::CompilerError'
W20190207-103913001[server.ChildProcess$LoggingStringHandler][server.ChildProcess$LoggingStringHandler.lambda$new$0] gapis:   what():  Over 3 compilation loops detected. Must be a bug!
@hevrard
Copy link
Contributor Author

hevrard commented Feb 7, 2019

This crash is due to spirv-cross crashing on a shader, this reveals three issues:

  • The GLES to GL conversion is called although we tried to replay on device, this conversion should not be triggered (TODO: invert condition on this line:
    if t.targetVersion.IsES {
    )
  • gapis should be robust to spirv-cross crashing
  • spirv-cross should be updated

@hevrard hevrard changed the title gapis crash when loading a capture gapis crashes when loading a capture Feb 7, 2019
@hevrard
Copy link
Contributor Author

hevrard commented Mar 11, 2019

spirv-cross crashes are gracefully handled thanks to #2600

@hevrard
Copy link
Contributor Author

hevrard commented Mar 11, 2019

It looks like spirv-cross has been last updated May of last year with:
https://github.com/google/gapid/pull/1871/files

Should we update it now?

In general, should we add update of third-party tools as part of a new release process?

@AWoloszyn
Copy link
Contributor

So, we typically only update third_party tools as necessary. There is quite a bit of effort needed in updating, and usually very little gain. If we think there is a specific reason we should update spirv-tools/spirv-cross/etc then we should. But otherwise it may end up being wasted work.

Given the number of dependencies we have, it would take O(days) to update them all properly. (llvm being the biggest problem here).

@AWoloszyn
Copy link
Contributor

In this case, we probably should update spirv-cross however.

AWoloszyn added a commit to AWoloszyn/gapid that referenced this issue Mar 13, 2019
AWoloszyn added a commit that referenced this issue Mar 13, 2019
@AWoloszyn
Copy link
Contributor

Updated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants