Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Sign in to follow this  
bay12

bug found?

Recommended Posts

Hi all, i think i've found a bug in start is back.

My configuration is: pc with 16gb of ram, window 10 1809 and startisback++ 2.9.

When the ram usage reaches 13/14gb and is approaching the limit of 16gb (this usually happens when i keep chrome open with loads of tabs for hours) windows tries to free up memory and i think something happens in the explorer.exe process.

From that point when i try to right click on any icon in windows taskbar, the right click menu doesn't' show up.

To fix this i have to restart the explorer process and everything goes back to normal.

I've done the same test deleting startisback and the issue IS NOT happening.

So i think it depends by startisback.

Can you guys try to re-create the issue and confirm if happens for you as well?

thanks all in advance

Share this post


Link to post
Share on other sites

27 minutes ago, jaclaz said:

If I were you I would first try to reduce chrome memory usage, besides the glitch in startisback you just reported, it is not a good thing to have 15 GB out of 16 GB used.

You can try The Great Suspender:

https://github.com/deanoemcke/thegreatsuspender

or The Great Discarder:

https://github.com/deanoemcke/thegreatdiscarder

jaclaz

thanks for your help.

I think i've found what is causing the issue: if i untick the box "do not prelaunch SearchUI and ShellExperienceHost processes" then even if the ram usage is 15 out of 16gb the right click functionality on the task bar remains there.

Hopefully this issue can be addressed and fixed by the developer though

Share this post


Link to post
Share on other sites

Do you use StartIsBack or standard jump list?

Share this post


Link to post
Share on other sites
1 hour ago, Tihiy said:

Do you use StartIsBack or standard jump list?

i use the standard jump list (the windows integrated one)

Edited by bay12

Share this post


Link to post
Share on other sites

Since you prevent ShellExperienceHost preload and jump lists are hosted there, it fails to start on demand when system is out of memory.

Since 1903 you may have different result since SIB does not affect ShellExperienceHost there. Likely you will have jump lists universally broken even without SIB :lol:

Share this post


Link to post
Share on other sites
1 hour ago, Tihiy said:

Since you prevent ShellExperienceHost preload and jump lists are hosted there, it fails to start on demand when system is out of memory.

Since 1903 you may have different result since SIB does not affect ShellExperienceHost there. Likely you will have jump lists universally broken even without SIB :lol:

Thanks for you answer.  So there's anything i can do or you can change in SIB to prevent this kind of behavior?

Edited by bay12

Share this post


Link to post
Share on other sites

Do not do what you do. You can't disable preloading of new UI and still use it.

Share this post


Link to post
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
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...