71

Vlad The issue lies in an inefficiency of Orion to handle the redrawing of its tabs - if my assumption is correct.

Thus, while less recognizable using 1 or 7 tabs, it is still present and consumes considerable more CPU than it should. Already with 1 tab, but adding up with more tabs.

I don’t think that using 50 tabs is far away from an advanced user having two windows with 25 tabs each open. Which exactly is the circumstance causing this issue.

  • dino replied to this.

      rosenrot please provide little more context

      1. Orion version
      2. macOS version

      Also, please try with latest Orion RC 126.4.1.8

          dino

          Sonoma 14.2.1 running the latest RC.

          The issue is present for almost a year or longer.

            dino Other than that please let me know if I can help. What would really be interesting to me is if you can reproduce it.

              14 days later

              @dino any update on this annoying bug? Have you been able to reproduce it?

              • dino replied to this.
                3 months later
                Merged 20 posts from Plugging an external display leads to high CPU usage of Orion.

                  Summary:
                  I am experiencing frequent browser freezing and high CPU usage, which forces me to forcefully quit the browser, resulting in the loss of important tabs. Due to the unpredictable nature of the issue, I am providing a Sample Process from Activity Monitor as it's the only available information I can provide.

                  Can sharing a Spindump file from the Activity Monitor help in understanding the problem better?

                  Steps to reproduce:

                  1. Open the web browser.
                  2. Keep a few tabs open.
                  3. Continue normal browsing activities.

                  Expected behavior:

                  • The web browser should operate smoothly without freezing or causing excessive CPU usage.
                  • Tabs should remain accessible and not be lost due to the browser freezing.

                  Orion, OS version; hardware type:
                  Version 0.99.125-beta (WebKit 616.1.22); MacBook Air (macOS Ventura 13.6 build 22G120)

                  Image/Video:

                  sample-of-orion.txt
                  165kB
                  • Vlad replied to this.
                    Leirk changed the title to Frequent Browser Freezing and High CPU Usage .

                      Leirk Can you please try OrionRC? (accessible if you join discord and ping me there, if you don't already have it) Also can you try with a clean new orion profile to rule out any extensions you may have installed fromc ausing this?

                          8 months later
                          Merged 3 posts from Frequent Browser Freezing and High CPU Usage.

                            Steps to reproduce:

                            • Open 30 tabs in Orion
                            • Make the device fall asleep
                            • Wake up the device and check CPU usage in the first 10-20 seconds
                            • Orion uses a lot of resources which leads to lags during the first 10-20 seconds
                              *It doesn't happen all the time, not sure yet how to reproduce but maybe others saw it as well

                            Expected behavior:

                            • Orion shouldn't require such CPU usage during waking up

                            Orion, OS version; hardware type:
                            0.99.123.3-beta, macOS 13.2.1, Macbook Air M2

                            Image/Video:
                            <Copy/paste or drag and drop to upload images or videos (up to 20MB)>

                              rosenrot Can you show a video of that (activity monitor?) And compare it to Safari in same circumstances?

                              Is this with or without extensions?

                                  Vlad without extensions. I just posted it here because it came to my eye several times last week as I use Orion as my daily browser.

                                  I need a little more time to reproduce and to compare to Safari. I thought it would make sense to post it here because maybe someone else experienced it already. This would help to narrow the potential issue.

                                  • Vlad replied to this.

                                      rosenrot I use Orion all the time as you can imagine across multiple laptops and do not have such issue. So we need to get to a reproducible state.

                                          Vlad Of course I'm certain that you use it every day.

                                          Actually, it doesn't happen when opening 30 tabs, putting the MacBook to sleep, and waking it up. It happens when I leave the laptop and it goes to sleep by itself. Meaning, when I return after an hour.

                                          I have to investigate a bit what the difference is between putting it to sleep and falling asleep by itself.

                                          Do you know if there are different treatments for apps regarding moving it to memory or something similar?

                                          I will post steps to reproduce as fast as possible.

                                            15 days later

                                            I'm also experiencing something very similar...

                                            After M1 Mac Mini goes to sleep (I usually don't force it to sleep, as I don't have a laptop lid to close, so it gets to time out on its own) next time I log in a huge amount of kernel_task activities are going on, spiking the CPU at around 100%, the amount of time is variable, but as a general rule of thumb the longer the Mac Mini has been sleeping the longer and also to some degree the more severe the issue is.

                                            Quitting Orion during this 100% CPU phase has so far always brought down the CPU usage of the kernel_task, so I'm not sure if it's swap or cache reloads or exactly what's going on behind the scenes.

                                            Today the Mac Mini had been allowed to sleep all day yesterday, so it was quite a drastic effect.
                                            A little slow to react I managed to take a screen shot of the Activity Monitor a little after I had quit Orion, which clearly shows the CPU graph taking a sharp dive:

                                            The leftmost mountain is while Orion was stil awake, and the within a second of Orion quitting and the processes dissapearing from the activity monitor the CPU usage disappears.

                                              Magebarf wonderful. I wasn’t able to reproduce this issue until now. What you say is what I experience as well.

                                              I have the impressions the more tabs are open the worse it gets besides sleep time.

                                              When my macbook wales up, the first seconds it is at 100% of cpu usage. Closing Orion vanishes the cpu usage for me as well.

                                              I tried to use some tools to trace cpu usage, maybe this is the way to go to provide information about this issue.

                                                  Woke the Mac Mini up this morning, same thing with CPU pegged at 100%, and this time I managed to catch the behavior that lead me to suspect Orion as one of the reasons the kernel_task is spiking as well:

                                                  The items I'm thinking about is all the "Orion Web Content" with or without "(Prewarmed)" suffix. After wake up, the entire visible dialog is only this type of process listed below the kernel_task, and only once the CPU loosens up a bit (which is the case in my screenshot, as the Cmd+Shift+5 screenshot tool won't really show up until there are some spare cycles) does other processes start being listed in the top when sorted by CPU. Also as you can see, the slope going down shows we're in the tail end of that CPU "sausage" in the graph...

                                                    Magebarf Nice! I posted this issue here with the hope that other people would experience it as well and that with joined effort we can identify the issue. Seems we are making progress.