New
#11
Do I read mocking? My friend and work computer are using drivers up to date and a regular Windows installation. I ask here since I don't find this behavior normal.
Do I read mocking? My friend and work computer are using drivers up to date and a regular Windows installation. I ask here since I don't find this behavior normal.
Hi
Maybe I can catch the culprit who is delaying your app startup if you can record a general trace using Windows Performance Recorder.
1/Start Windows Performance Recorder, then begin recording a trace using the following params:
2/ After starting recording, run your application so that the recorder catches the delay.
3/ Stop recording after your application launches.
4/Compress the trace file (.ETL) and share it here.
5/ Cross fingers
Hope I did it right! :)
Here is the link for ETL file: WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free
Here is the link for the folder/archive: WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free
I tried only launching Photoshop while recording.
Here the ZIP. Thanks: WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free
To better understand the issue, you said that the delay you are experiencing happens between the time you launched the app and when the app window appears.
When you recorded the trace, did you visually notice the delay when launching Photoshop?
Yes it happens with all adobe apps - waiting then the app window. It doesn't happen on my work computer (which is slower) or my friends computer. They launch instantly there (the window).
Other apps also experience slow launches like the first time I open Chrome for example.
Yes, when I recorded the trace I waited few seconds before the PS logo.
With Adobe products - every time. Chrome starts instantly the second time.
In the trace, I see a delay of about 3 seconds before the Adobe app GUI appears. Is that what you noticed also?
But I don't see another process (e.g. antivirus...etc.) delaying the Adobe launch. What I see is just Photoshop loading its programs and DLLs!
Another test we can do is to restart a computer and record a trace when launching Chrome for the first time. Maybe we can see something interesting in the trace.