Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

AbdullahS23

macrumors newbie
Original poster
Apr 20, 2022
4
0
Got my first mac about a year ago and it happened to be an M1 air. Heard a lot about how the m1 chip is absurdly fast and I back that. Coming from windows, I'm thoroughly impressed by the speed of the m1 when it comes to launching some apps but unfortunately I haven't had the same experience with Chrome and VLC and ironically these are my most frequently used apps. Let me start with the smaller problem(VLC). I've used cheaper, inferior windows machines and almost all of them seemed to open vlc in the blink of an eye. That's not the case with m1. It took me about five to six bounces to launch vlc but that was before me reading an article of someone having a somewhat similar problem with their m1. One of the solutions read to ping ocsp.apple.com which I tried and it turned out to being successful. Since then vlc has been taking 3 bounces to load which is still pretty slow compared to windows but somewhat manageable. Now coming to the main headache. Chrome takes about six bounces to load which is slow to the point where it pinches. Reinstalling fixes the problem but not permanently. Initially it takes about less than a bounce to load but about one week after reinstalling, the problem comes back. Pinging whatever the heck ocsp is fixed the problem but again only for about a week and now even it doesn't have any effect. i know these problems are not the end of the world but considering how much marketing apple is putting into these it doesn't seem fair. and yes both these apps are running natively on the m1 chip. any help would be highly appreciated.
 
These problems are most likely caused by design choices made by the developers of these two apps. Not a lot anyone here can do to help, your best bet (which still might not have any effect) is to submit feedback asking for faster startup time to videolan.org and Google.

BTW, I see the slow initial launch of VLC but after that's happened, if I quit and relaunch, it opens in a blink.
 
These problems are most likely caused by design choices made by the developers of these two apps. Not a lot anyone here can do to help, your best bet (which still might not have any effect) is to submit feedback asking for faster startup time to videolan.org and Google.

BTW, I see the slow initial launch of VLC but after that's happened, if I quit and relaunch, it opens in a blink.
Because the application is cached in memory after the first launch.
 
Got my first mac about a year ago and it happened to be an M1 air. Heard a lot about how the m1 chip is absurdly fast and I back that. Coming from windows, I'm thoroughly impressed by the speed of the m1 when it comes to launching some apps but unfortunately I haven't had the same experience with Chrome and VLC and ironically these are my most frequently used apps. Let me start with the smaller problem(VLC). I've used cheaper, inferior windows machines and almost all of them seemed to open vlc in the blink of an eye. That's not the case with m1. It took me about five to six bounces to launch vlc but that was before me reading an article of someone having a somewhat similar problem with their m1. One of the solutions read to ping ocsp.apple.com which I tried and it turned out to being successful. Since then vlc has been taking 3 bounces to load which is still pretty slow compared to windows but somewhat manageable. Now coming to the main headache. Chrome takes about six bounces to load which is slow to the point where it pinches. Reinstalling fixes the problem but not permanently. Initially it takes about less than a bounce to load but about one week after reinstalling, the problem comes back. Pinging whatever the heck ocsp is fixed the problem but again only for about a week and now even it doesn't have any effect. i know these problems are not the end of the world but considering how much marketing apple is putting into these it doesn't seem fair. and yes both these apps are running natively on the m1 chip. any help would be highly appreciated.
What do you mean by "pinches" and "pinging"?

Launching apps is not a benchmark technique that I've ever seen before. Interesting. ?
 
  • Like
Reactions: Tagbert
Because the application is cached in memory after the first launch.
No, that's not it. VLC is not a huge app, the bundle's 115MB. About 38MB of that is localizations for a ton of languages, you only need / read one. Most of the rest is dynamic libraries, one per video codec VLC supports. So realistically very little of it needs to be read on launch.

I didn't time it but the first launch was at least 5 seconds, maybe as much as 10. Reading less than 100MB from the internal SSD of a M1 should be under 100ms, tops.
 
  • Haha
Reactions: basher
i know for the microsoft office products, the number of bounces are different depending on whether they were purchased directly from microsoft or through the app store. the ones purchased directly from microsoft have more bounces while gatekeeper does it's job. the ones from the app store are already verified ala gatekeeper and have less bounces apparent during the launch process
 
Chrome has been launching very slowly on my m1 Mini since the Chrome version 100 update.
 
i agree, for some reason, VLC startup (even when it has been used recently, but not 5 secs ago) is very slow (5+ secs) on M2
 
On my M1 mini VLC takes 2-3 seconds with fresh, uncached launch. Which is ... kinda slow. Chrome is faster, despite reopening a bunch of tabs.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.