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

[Bug] Automation scripts are loaded twice at startup #15

Closed
Akatmks opened this issue Nov 15, 2022 · 2 comments
Closed

[Bug] Automation scripts are loaded twice at startup #15

Akatmks opened this issue Nov 15, 2022 · 2 comments

Comments

@Akatmks
Copy link

Akatmks commented Nov 15, 2022

Steps to reproduce

  1. Prepare an Aegisub DC installation next to arch1t3cht/Aegisub installation.
  2. Add a reasonable amount of automation scripts into the automation folder of both Aegisub.
  3. Use a stopwatch to time the startup for both Aegisub.

What should happen?

It should take roughly the same time to start either version of Aegisub.

What has happened?

arch1t3cht/Aegisub takes twice as much time to start as Aegisub DC.

Software version

Tested on Aegisub 2317062 and 3aeca6d Windows portable installation.
Windows 11 Home 21H2.

My guesses

I noticed that every automation script is listed twice in arch1t3cht/Aegisub's automation menu (I don't mean scripts written in MoonScript; Those are listed four times). I assume this is the cause to the slow startup.

Thank you!

@arch1t3cht
Copy link
Owner

This is probably the same as TypesettingTools#168 . In particular, it only comes up in the portable build by default, and can be circumvented by changing the autoload path under Preferences > Automation. We discussed possible solutions back then, the simplest one just being deduplication of the autoload paths. But I didn't implement this yet, mostly because this seemed like more of a workaround than a fix. But I'll see if I can implement this now or find a better solution.

@arch1t3cht
Copy link
Owner

It turns out that the above commit didn't properly fix this, so reopening for now. Will fix soon.

@arch1t3cht arch1t3cht reopened this Sep 17, 2023
arch1t3cht added a commit to TypesettingTools/Aegisub that referenced this issue Dec 3, 2023
arch1t3cht added a commit to TypesettingTools/Aegisub that referenced this issue Dec 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants