You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I agree to follow the Code of Conduct that Ferdium Recipes adheres to.
I have searched the issue tracker for a bug report that matches the one I want to file, without success.
Ferdium Version
6.7.2-3
Recipe Name
Instagram
Recipe Version
2.5.3
Last Known working version of the recipe
No response
Steps to reproduce
Open Instagram service, with hibernation enabled
Go to the homepage
If necessary, scroll down to one of the auto-playing videos
Switch to another service
Expected Behavior
With hibernation enabled, I expect the service to hibernate eventually. I also expect to be able to trigger hibernation myself via the service context-menu.
Actual Behavior
Neither expectations hold true; the hibernate service action is disabled.
Screenshots
No response
Additional Information
I noticed this because my fans kept blowing, and top showed Ferdium to be the culprit.
I never noticed this before (but I have always been pretty systematic in switching back to the less resource-hungry DM page before switching to a different service).
The text was updated successfully, but these errors were encountered:
Preflight Checklist
Ferdium Version
6.7.2-3
Recipe Name
Instagram
Recipe Version
2.5.3
Last Known working version of the recipe
No response
Steps to reproduce
Expected Behavior
With hibernation enabled, I expect the service to hibernate eventually. I also expect to be able to trigger hibernation myself via the service context-menu.
Actual Behavior
Neither expectations hold true; the
hibernate service
action is disabled.Screenshots
No response
Additional Information
I noticed this because my fans kept blowing, and
top
showed Ferdium to be the culprit.I never noticed this before (but I have always been pretty systematic in switching back to the less resource-hungry DM page before switching to a different service).
The text was updated successfully, but these errors were encountered: