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

Black screens are captured while capturing android launcher3 #825

Closed
digish opened this issue Jul 28, 2017 · 5 comments
Closed

Black screens are captured while capturing android launcher3 #825

digish opened this issue Jul 28, 2017 · 5 comments
Assignees
Milestone

Comments

@digish
Copy link

digish commented Jul 28, 2017

With the first pre-built release for windows msi package.
I am trying to capture the android launcher process trace for debugging one gles corruption issue.

It captures the gl/egl calls frame by frames.
but does not show the frame buffer dumps and draw output. it just shows black in top preview pane and
in detailed view transparent

Attaching the trace for checking.

launcher3_20170728_1636.zip

@ben-clayton
Copy link
Contributor

Hi @digish - thank you for the capture.
I can open this trace and inspect the frames. I see launcher icons, but before it gets to that, there are a number of frames with a sliding black texture.

screen shot 2017-07-28 at 12 56 14 pm

Is your issue with this black texture?

I want to check we're both seeing the same thing before I go any further.

@digish
Copy link
Author

digish commented Jul 28, 2017

thanks for update ben,
I just checked again the captured trace on both mac and windows.
On mac it is showing as expected.
but on windows same trace is not shown only black screens and after few frames only exclamation symbol icon but not actual rendered screen.

it seems windows version has some issue.

@ben-clayton
Copy link
Contributor

That's interesting. Is there anything in the report view or log view that suggests some sort of replay error?

It would be useful to know the graphics driver and GPU model in your windows machine. This can be found using gapit.exe devices in the installation path of GAPID. Please don't copy anything you're not happy to share!

Many thanks,
Ben

@digish
Copy link
Author

digish commented Jul 28, 2017

Attaching the gapit.exe device output for the windows machine where i am running gapid
log.txt

it shows GPU vendor as unknown but
in device manager i can see two display adapters
Intel HD graphics 4000 and
NVIDIA NVS 5400M

--
this is how the same trace looks on my windows machine
image

@ben-clayton ben-clayton self-assigned this Aug 1, 2017
@ben-clayton ben-clayton added this to the V0.9 (Beta) milestone Aug 1, 2017
ben-clayton added a commit to ben-clayton/gapid that referenced this issue Aug 1, 2017
ben-clayton added a commit to ben-clayton/gapid that referenced this issue Aug 1, 2017
ben-clayton added a commit to ben-clayton/gapid that referenced this issue Aug 1, 2017
@digish
Copy link
Author

digish commented Aug 3, 2017

Thank you ben for the fix.

purvisa-at-google-com pushed a commit that referenced this issue Sep 29, 2022
…825)

Cleanup details:

- Remove all obsolete configs that do not appear anywhere else in the
  code.

- Also remove DebugDependencyGraph since
  dependencyGraphBuilder.debug() was never used, and seemed to be a
  leftover from some debugging session

- Set DumpValidationTrace to false, as we don't want this to be set in
  our dev-release builds

- Add a proper documentation for each config option

Bug: n/a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants