Bug 464623 - Seem like it will cause Youtube on brave lag and stutter if is open as main window
Summary: Seem like it will cause Youtube on brave lag and stutter if is open as main w...
Status: RESOLVED NOT A BUG
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: 5.1.5
Platform: Other Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-21 23:24 UTC by sinyceronoendo
Modified: 2023-06-22 13:48 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description sinyceronoendo 2023-01-21 23:24:49 UTC 
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Open krita
2. Open brave browser and play a video on youtube
3. switch back to krita

OBSERVED RESULT
Youtube get lag and stutter, is fine if switch back to Brave, but will begin lagging if switch back to Krita

EXPECTED RESULT
It should be no lag at all. 

SOFTWARE/OS VERSIONS
Krita

 Version: 5.1.5
 Installation type: installer / portable package
 Hidpi: true

Qt

  Version (compiled): 5.12.12
  Version (loaded): 5.12.12

OS Information

  Build ABI: x86_64-little_endian-llp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: winnt
  Kernel Version: 10.0.19044
  Pretty Productname: Windows 10 (10.0)
  Product Type: windows
  Product Version: 10

ADDITIONAL INFORMATION
This happen, either after i update to 5.15, or after i change hardware . Both happen almost in the same day.
Comment 1 Halla Rempt 2023-06-22 13:48:37 UTC 
Sorry, this is not a bug in Krita. Applications need a certain amount of CPU, and that can cause performance problems in other applications that get starved of resources. There is not something special about the interaction between that browser and krita, and nothing in Krita's code we can change to fix this issue.