Jump to content

Script takes a long time to load after it is built


 Share

Recommended Posts

I have a script using GUI that takes a long time to load after it's been built. If I run the script from the script editor it opens almost instantly. If I build the script then run the exe, it takes up to 30 seconds to load. The file itself isn't very big @483kb. Here is the list of includes:

#include <GUIConstantsEx.au3>

#include <GUIComboBox.au3>

#include <StaticConstants.au3>

#include <EditConstants.au3>

#include <OutlookEX.au3>

#include <Date.au3>

#include <WindowsConstants.au3>

#include <GUIComboBox.au3>

#include <mysqllite.au3>

#include <DateTimeConstants.au3>

#include <ad.au3>

I tried setting a splash screen to at least show a loading window when the tool is coming up, but it just flashes instantly then loads the screen after waiting to load. So it appears as though the issue is there is a delay loading the file into memory and starting the script, not the script running slowly itself. I've also tried this on other computers, same result though the load time varies. Any thoughts on this?

Link to comment
Share on other sites

Well, as far as I understood you excluded it only. Have a look to the cpu usage and which app cause the high cpu load when you start your compiled script.

Our company is using the mf Mc Affee which is configured bullshit. Each time I start my exe it takes a while. The av scans the exe again and again and again...

I put one of my apps to a usb and started it directly from the stick. Guess how long it took!

Br,

UEZ

Edited by UEZ

Please don't send me any personal message and ask for support! I will not reply!

Selection of finest graphical examples at Codepen.io

The own fart smells best!
Her 'sikim hıyar' diyene bir avuç tuz alıp koşma!
¯\_(ツ)_/¯  ٩(●̮̮̃•̃)۶ ٩(-̮̮̃-̃)۶ૐ

Link to comment
Share on other sites

  • 3 weeks later...

For anybody else who stumbles across this, the problem was indeed related to Symantec Endpoint Protection 12.1, see this thread below:

The problem is with the SONAR engine scan while UPX compression was enabled while compiling the exe. The fix for me was:

1. In Aut2Exe go to Compression > Uncheck "UPX Compress .exe Stub"

2. Check the box for x64 - The first time I tried I didn't check this, and it didn't fix it until I checked it the 2nd time

3. Create an application exception in SEPM and push to your clients if you're in a domain environment.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...