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

[Security Solution] Safari browser (13.1.2) crashed on setting per page to 300 under detection rules #84608

Closed
ghost opened this issue Dec 1, 2020 · 7 comments
Assignees
Labels
bug Fixes for quality problems that affect the customer experience impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. QA:Validated Issue has been validated by QA Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. triage_needed v7.14.0

Comments

@ghost
Copy link

ghost commented Dec 1, 2020

Describe the bug
Safari browser crashed on setting per page to 300 under detection rules

Build Details:
Platform: Production
Version:7.10.1 BC1
Commit: 1d4cfde288ede0c4bc6277b4d589ca0cb96b231f

Artifact Page : https://staging.elastic.co/7.10.1-ce3b40e6/summary-7.10.1.html

Browser Details
Safari: 13.1.2(13609.3.5.1.5)

Preconditions
1.Cloud environment having version 7.10.1 BC1 on production should exist

Steps to Reproduce

  1. Navigate to Kibana url on Browser.
  2. Click "Security" from the left navigation bar.
  3. Go to detection tab and click on "Manage detection rules' button.
  4. Scroll page down and change the per-page to 300.
  5. safari browser crashed and webpage becomes unresponsive . Additionally after some time error is thrown of high memory usage

Note: Issue is occurring on Physical Hardware machine [ High Sierra]

Test data
N/A

Impacted Test case(s)

Actual Result
User not able to set per-page to 300 under detection rule for Safari browser

Expected Result
User should be able to set per-page to 300 under detection rule for Safari browser

What's Working

  • issue is not occurring on all windows browsers
  • issue is not occurring on Chrome[MAC]

What's not Working

  • N/A

Screenshots

  • Manage detection rules list

image

  • per page

image

  • web page becomes unresponsive

image

  • browser version

image

Logs
N/A

@ghost ghost added bug Fixes for quality problems that affect the customer experience Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. labels Dec 1, 2020
@ghost ghost assigned manishgupta-qasource and ghost Dec 1, 2020
@ghost ghost added the Team:Threat Hunting Security Solution Threat Hunting Team label Dec 1, 2020
@ghost
Copy link
Author

ghost commented Dec 1, 2020

@deepikakeshav-qasource please review

@ghost ghost added the impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. label Dec 1, 2020
@ghost ghost assigned MadameSheema Dec 1, 2020
@ghost
Copy link

ghost commented Dec 1, 2020

Reviewed & Assigned to @MadameSheema

@MadameSheema MadameSheema added Team:Detections and Resp Security Detection Response Team and removed Team:Threat Hunting Security Solution Threat Hunting Team labels Dec 1, 2020
@MadameSheema
Copy link
Member

@peluja1012 @spong can you please help to prioritise this? feel free to change the impact if you don't agree with it :)

@spong spong added the v7.11.0 label Dec 1, 2020
@MadameSheema MadameSheema added impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. and removed impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. labels Jan 21, 2021
@dontcallmesherryli
Copy link

@karanbirsingh-qasource please validate this again on the latest snapshot so we can triage. Thank you!

@ghost
Copy link
Author

ghost commented Apr 15, 2021

Hi @MadameSheema

we have validated this issue on 7.12.1 and found that issue is still occuring , webpage becomes unresponsive on changing pagination to higher number like 300 and 600.

Note: issue not occuring on Firefox and chrome browser of same mac machine.
image

Machine Details
image

Build Details:

Version: 7.12.1
Commit:bb662886fc93cd04030e66223bb1ffa8512e0705
Build : 39445

Snap-Shoot:
image

thanks !!

@peluja1012
Copy link
Contributor

@karanbirsingh-qasource As of this PR, we only allow users to display up to 100 rules at a time. Do you see similar issues with 100 rules in Safari?

@ghost
Copy link
Author

ghost commented Jun 23, 2021

Hi @peluja1012

thanks for sharing the updated paging change.

we have validated this issue on 7.14.0-SNAPSHOT and found it fixed . Now user is able to set row per page to 100 and can view details of all 100 detection rule in mac safari browser.

Build Details:

Version: 7.14.0-SNAPSHOT
Commit:e26582638988179d134e77e59b66ed8f982ab064
Build:41896

Snapshot:
image

Hence we are closing this issue.

c.c @MadameSheema

@ghost ghost closed this as completed Jun 23, 2021
@ghost ghost added the QA:Validated Issue has been validated by QA label Jun 23, 2021
This issue was closed.
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 impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. QA:Validated Issue has been validated by QA Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. triage_needed v7.14.0
Projects
None yet
Development

No branches or pull requests

6 participants