Check Memory usage

Vlad That's what I was trying to say -- it is reproducible in that it always ends up that way but it happens over extended sessions so I don't have a concise set of steps to reproduce.

Almost the opposite in that if I have Orion set to save my session and reopen the same on startup, the restarted Orion uses a lot less memory than what Orion was using just prior to quit with the same windows. As you can see in the snapshot, there were 0 windows/tabs open but still 13 processes and 3GB of RAM being used after I closed all tabs/windows after an extended session before I quit. A fresh Orion session starts out at _150MB.

I realize that doesn't give you a lot to go on which I was asking for additional things I can capture when this happens. Or additional options I can give Orion before starting an extended working session so that I can give you more debugging info once it does happen.

Vlad Okay I admit I didn't know there are 2000 other issues out there... If you have suggestions on how an end-user can track down issues like this much appreciated. I am happy to do the legwork.

By the way the good news is that most of the easily reproducible crashing bugs in Orion have been squashed. The bad news is that leaves intermittent ones with no obvious sequences to reproduce...

Side note: I had two crashes in Orion recently -- both SEGV and I assume from null pointer dereferencing as the crash report included a message along the lines of "KERN_INVALID_ADDRESS at 0x0000000000000110". However the crashes appeared to be in the WebKit thread (both times under WKImmediateActionController immediateActionRecognizerWillPrepare). I assume that normally crashes in WebKit are best reported directly to that project though does that still hold for the Mojave/Catalina builds?

bzgnyc

Okay I admit I didn't know there are 2000 other issues out there...

There are 2786 issues open at this moment to be exact! Good news is we squashed 3289 issues so far!

If you have suggestions on how an end-user can track down issues like this much appreciated.

The details of what we need to fix this are explained in this post:

https://orionfeedback.org/d/4480-check-memory-usage/54

Am I correct that after 74 posts here we still have not one with exact steps to reproduce as per https://orionfeedback.org/d/4480-check-memory-usage/54 ? Or we are missing something - please advise.

It has to do with Orion letting the sites still run in the background while on another tab. Other browsers have the option to disable that.

The websites I surfed on usually consists of those with a live chat as upwork and sites running on React (Next.js)

Vlad Other than the one memory runaway example that I provided that was Mojave-specific (also reproducible under Catalina but for some reason at a much lower level), I agree there is a gap. I understand that you need a concise set of steps to reproduce so that you can investigate and fix. We don't have that. However please understand that many users consistently experience high memory usage when Orion is left running for a while but we're not sure the exact steps that lead up to that situation as it typically takes place over a several days.

However, as my screen capture shows there is a leak and what appear to be multiple zombie processes. I had no windows/tabs open at that moment in the session and yet there were still 13 Web Content processes and Orion's main process was using 3GB of memory.

What we need -- what I was looking for -- is some advice or additional tools to bridge the gap. As I noted I'm happy to do the legwork but it's unclear to me (and it appears for others as well) how to approach this problem when things start out great but slowly blow up after 2-3 days of browsing.

Perhaps what we need to do is regroup on this. Like all the diagnostic tools most OS accumulate as they mature perhaps more tools are needed in Orion for end-users to help isolate issues like this for reporting. I will work on some ideas and post in Suggestions this weekend.

P.S.When you said there were 3K issues I believed you. Just surprised because previously I never would have guessed that amount from previous browsing of the Roadmap. Plus I just don't experience that many issues on a day-to-day basis. Yes I experience several Mojave-specific issues and this amorphous problem but it really doesn't feel like a browser with 3K open issues...

bzgnyc I had those problems since launching Orion without browsing for 2-3 days.

Xytronix Steps to reproduce please

bzgnyc You have a point we will see if we can come up with instructions/tips to better hunt this down. We agree that there is likely an issue and are keen to get this sorted out.

Subject: High RAM Usage Issue with Orion Browser Installation

Dear Orion Support Team,

I am reaching out to report an unusual issue with RAM usage in the Orion browser, which I recently installed on my device.

Despite having only one extension active—Ghostery, installed via the Chrome Web Store and taking up around 300 MB of storage—the browser displays a progressively increasing RAM consumption. With no webpages open, Orion initially starts at approximately 500 MB of RAM but then gradually rises. Within two minutes, the usage reaches around 4 GB, and at times it has escalated to 9, 10, or even 11 GB with only one or two pages open.

This behavior seems abnormal, particularly for a fresh installation. I have attempted various solutions, but the issue persists. Could you please provide any guidance on addressing this situation? Additionally, I would appreciate knowing if this is a known problem or if there may be specific compatibility issues on my system.

Thank you for your attention and any support you can provide.

Best regards,
Matteo

I would also like to mention that I expected Orion to perform as advertised, particularly in terms of efficiency. Currently, however, it is the least RAM-efficient browser I have encountered. I had hoped it would fulfill its promise of being extremely resource-efficient, but as it stands, it falls far short in this regard. I even tried reinstalling and adjusting settings, but the problem remains unresolved.

Orion v129

Sequoia (15)

Hello,

I recently switched from Arc to Orion, but it appears to consume more memory even with fewer tabs open. I have also disabled the add blocker list. Tomorrow, Orion was using over 12 GB of memory with 10-15 tabs open, while Arc, with 20+ tabs and 5-6 pinned tabs, I have over 100 suspended tabs in a folder, and arc was using 8-9 GB of RAM.

Therefore, I decided to conduct a one-on-one comparison to determine if Orion is equal to Arc, but sometimes consumes more memory. Arc retains the same tabs from the previous day, while Orion retains approximately 20 tabs.

I also compared Orion to Safari, and Orion consumed slightly more memory. I noticed a lagging performance while using Orion for both comparisons.

Every time I use I Orion I get it using high memory notification from clean my mac. Mostly it happens to me when I'm using Figma, but never happens with any browser.

Orion vs Safari - https://youtu.be/6BYW0762iYM
Orion vs Arc - https://youtu.be/posA-BF-D5g

Despite liking Orion, memory optimization is the most important priority.

OmkarBirje I conducted a test using the browser without any extensions, and it performed well with no lag, even though I had over 40 tabs open. In comparison, Arc had only 4-5 tabs open.

The memory usage was as follows: Orion Browser used 7.18 GB, while Arc used 5.65 GB.

Based on this, I believe that using this browser without extensions allows it to function effectively.