LSS-Manager / LSSM-V.4

The Official Repository for LSS Manager V4
https://lss-manager.de
Other
56 stars 92 forks source link

[BUG]: LSSM crashing missionchief.com site #2312

Closed omer19800 closed 1 year ago

omer19800 commented 1 year ago

What happened?

hey all, sorry to open it here but discord link is unavailable for me i downloaded LSSM a few months back, downloaded some plugins, had some fun and then one day i opened mission chief with LSSM turned on and the site went unresponsive after the initial loading, and then crashed with chrome offering to either exit or wait (after 15+ minutes i gave up) tried reinstalling LSSM with no change, reinstalling tampermonkey also with no change. LSSM from the userscript - // ==UserScript== // @name LSS-Manager V.4 // @version 4.7.4 Tampermonkey - same

my guess is i just loaded up too many plugins, (would be more than happy to send LSSM logs - just let me know how) and the basic solution would be to hard reset my LSSM but i couldnt figure it out on my own

How to reproduce?

  1. go to missionchief.com
  2. turn on LSSM through the tampermonkey chrome extension window
  3. refresh missionchief.com
  4. site crashes

Expected behavior

LSSM working normally

System

Additional

No response

jxn-30 commented 1 year ago

That is very sad to hear but thanks for the bug report!

To identify the issue better, there are some more information we would like to know:

Normally, there should not be a limit of Modules enabled within LSSM. The issue sounds more like an accidental endless loop. LSSM itself does not log anything so there is nothing to send ;)

Hard Reset LSSM: LSSM stores settings within IndexedDB in the browser. This is a feature-rich form of local storage for webapplications. It can be accessed in Chrome by pressing F12 and heading to the Application tab. On the left side in the navigation under section Storage you will find IndexedDB. Open the tree-menu until you see the DB called lssmV4Storage. Now search for the activeModules row, right click it and press Delete. This will disable all modules but your settings will not be lost. Enable LSSM and reload the game and see if it works now. You can then enable modules one by one to test if there is a single module causing the issue. If that didn't work – the game still crashes, do the same thing for settings_global row. Before deleting it, check in the Value column, if debugMode is set to true. If yes, delete the row and try again, otherwise deleting the row will most likely not bring any improvement. If it still crashes, try deleting the whole database. In the left treeview, select the lssmv4 - https://www.missionchief.com/ entry, you will see an overview site for the database, including a button to delete it. To be sure, everything is cleared, also head to the Local Storage and Session Storage and in the https://www.missionchief.com/ entry, delete all rows where the key starts with lssmv4. Now re-enable LSSM and reload the game. Hopefully everything should work now because you successfully did a hard-reset of your LSSM.

omer19800 commented 1 year ago

thanks for the quick answer! 1) LSSM is the only script I have running on Tampermonkey 2) in total - around 110 for a rought estimate awesome - deleted the activeModules and everything seems to work right, seems it fixed it perfectly, will update if I discover what the problem was thanks for the help! appreciate it

Cr4zyc4k3 commented 1 year ago

Gonna close this since it seems to work. But if that behavior reoccurs feel free to reopen this issue