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

[Reporting] Investigate cause of screenshot capture timeouts on Windows #63073

Closed
tsullivan opened this issue Apr 8, 2020 · 6 comments
Closed
Labels
bug Fixes for quality problems that affect the customer experience (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:large Large Level of Effort

Comments

@tsullivan
Copy link
Member

tsullivan commented Apr 8, 2020

Kibana version: 6.8, 7.1

Elasticsearch version: 6.8, 7.1

Server OS version: Windows Server

Browser version:

Browser OS version:

Original install method (e.g. download page, yum, from source, etc.): download page

Describe the bug:

When a user tries to generate a report, the Reporting plugin succeeds in opening the page and scanning the DOM for visualization elements. When all visualizations have signaled rendering is done, Reporting attempts to capture a screenshot, and it times out.

Steps to reproduce:

  1. So far, we have been unable to reproduce the issue in controlled environment
  2. Having Cisco AMP for Endpoints and Tripwire Enterprise Agent installed might be necessary to reproduce the bug.

Expected behavior:

Screenshots (if relevant):

Errors in browser console (if relevant):
No errors logged from Puppeteer's screenshot function. The reporting job fails due to time out.

Provide logs and/or server output (if relevant):

Any additional context:

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-reporting-services (Team:Reporting Services)

@tsullivan tsullivan added the bug Fixes for quality problems that affect the customer experience label Apr 8, 2020
@tsullivan
Copy link
Member Author

tsullivan commented Apr 9, 2020

For reference, this is the method that appears to be blocked: https://github.com/puppeteer/puppeteer/blob/21c2d31/docs/api.md#pagescreenshotoptions

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-services (Team:AppServices)

@ppisljar ppisljar added impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. loe:x-large Extra Large Level of Effort labels Apr 29, 2021
@ppisljar ppisljar added the (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead label May 10, 2021
@exalate-issue-sync exalate-issue-sync bot added loe:weeks loe:large Large Level of Effort and removed loe:x-large Extra Large Level of Effort loe:weeks labels May 13, 2021
@tsullivan
Copy link
Member Author

I'm still able to reproduce this on Windows 10 using a build candidate of the latest master branch.

System stats:

  • 64G ram
  • 12 core
  • 4GB GPU

I don't understand why a decently provisioned system like this is unable to render a dashboard which Linux can, when booted on the same hardware. But I also experience general slowness with the Windows system overall, and I don't know why.

@tsullivan
Copy link
Member Author

This is possibly fixed in the latest version of Kibana that uses a newer version of Chromium.exe

@exalate-issue-sync exalate-issue-sync bot added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. and removed impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. labels Aug 11, 2021
@tsullivan
Copy link
Member Author

This seems to be no longer an issue as of #98688

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:large Large Level of Effort
Projects
None yet
Development

No branches or pull requests

4 participants