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

Boot time nearly doubled with burn my windows extension enabled #458

Open
unvaluablespace opened this issue Oct 25, 2024 · 3 comments
Open
Labels
bug Something isn't working

Comments

@unvaluablespace
Copy link

Describe the Bug
With burn my windows installed and enabled, my boot time from power on to desktop is about 45-50 seconds. Normally boot time is only 22 seconds.

Steps to reproduce the behavior:

  1. Add "Burn-My-Windows" gnome extension and enable it.
  2. Shutdown PC. Then, with a timer, press power button and start timer at the same time
  3. Stop timer as soon a desktop appears. (I have autologin enabled)
  4. Uninstall Burn-My-Windows, repeat steps 2&3. Compare time difference.

Tried testing to see if specific burn my windows effects made a difference, but even just enabling only 1 effect seemed to increase overall boot time. I've got like 15 other GNOME extensions and separately tested boot difference with everything else enabled/disabled. Only Burn-My-Windows seems to add almost double the boot time.

System

  • Fedora 40 & recently 41
  • Burn-My-Windows version [latest version]
  • GNOME Shell version: [47]
@unvaluablespace unvaluablespace added the bug Something isn't working label Oct 25, 2024
@Schneegans
Copy link
Owner

Schneegans commented Oct 25, 2024

Thanks for the report, but this is almost certainly impossible.

GNOME extensions are enabled at login time. So the only thing that could be affected is the time it takes from the login screen to the desktop. Please time this instead - disable auto login and measure the time it takes from entering your password to the point where you see the desktop.

That being said, I still think that it is very unlikely that it makes any difference. Only very little code runs when the extension is enabled (and that is what happens when you start your session). You can also enable the extension in the extensions app and see how long it takes to flip the switch. I think there is a noticeable delay, but it's well below a second.

@unvaluablespace
Copy link
Author

So this is certainly interesting... I just tried with auto login disabled, and timing from entering password to desktop just like you asked, and it looks to be about the same time with burn my windows enabled/disabled. So, curiuosly, I decided to time it from power off to the login screen, which times to about 25 seconds (not counting timing from password to desktop) the same time with and without burn my windows. So I turn autologin back on, and like I originally mentioned, the time doubles with burn my windows enabled. Disabled, it takes about 25 seconds from power off to desktop, but then doing the same with burn my windows enabled, extends the boot up time to 45 seconds.

I have plenty of other things loaded, but none of it increases the boot time when using autologin, only when burn my windows is enabled. but then again, disabling auto login seems to reduce the boot time if burn my windows is enabled. I do notice that the fedora splash screen seems to be taking longer to load before the desktop loads. I will look into this further.

I am not very good with Linux yet, so I am not sure how to troubleshoot login performance, but I will dig into this further. Sorry for the confusion.

@Schneegans
Copy link
Owner

journalctl -b > log.txt

Will write the system log since the last boot to a file called log.txt. Maybe you can create such a file with the long and the short boot time and look for differences?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants