-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
High Resource Usage #12
Comments
I'm trying to Windows 10 but I can't reproduce the issue. |
Hello mat, This is a config file from one of our customers experiencing this issue with our your plugin.
|
Hi Alex, Thank you! |
I reproduced the issue and... Yes, it only happens on linux OS. I need more time to debug it. |
Hi Alex, after some tests, I found the cause. It is caused from the library "libasynql" that manage the database. Unfortunately, I can't fix the issue because it does not depend from me. The library's author is already aware. |
R.I.P |
Yes, I have seen the new version of libasynql. I am currently working on a new version of BedcoreProtect v0.6.0 which aims to improve even more the performance and contains many bug fixes so far undiscovered! |
Hi @AlexPads and @enescaglayan, I am offering you a usable beta version of BedcoreProtect v0.6.0 to check if this issue persists.
Please, let me know. Thanks in advance. |
# Introductory notes - **This update is recommended because it contains many improvements and bug fixes.** - The update is backward compatible with **v0.5.x** - If you are already using BedcoreProtect **v0.5.x** and you upgrade to **v0.6.0, you will notice a message of database upgrading**. Don't worry, that's normal. It's the patch manager process that updates the database tables for the new version. **If during the process you got a crash, please open a issue [here](https://github.com/matcracker/BedcoreProtect/issues/new/choose)!** # Changelog (Last update: 08/05/2020) The update is not finished yet and the changelog could be updated in any time. ## Features - Added /bcp undo command _(Permission: bcp.subcommand.undo)_. Allows to undo the last rollback/restore. - Now block restrictions works. So, is now possible to include/exclude certain blocks during a rollback or a lookup. - When a player spawn an entity through a spawn egg is now logged. - When a entity dies due to a block (e.g. fire, lava, etc...) is now logged. - When a player ignites a TNT is now logged. - Code analyzed with PHPStan level 8. ## Improvements - With SQLite the data will be saved every 5 minutes (same as worlds) instead of 5 hours. - Re-wrote query execution code getting a speed up! - Most of queries when executed are now scheduled in order by preventing missing or wrong logs. - Improved the QueryGenerator execution. - Improved painting break tracking. - Removed tiles when rollback placed blocks. - General minor improvements. ## Changes - The patch manager is now able to patch a different numbers of patches for each database type. - From now in the database version of status command (/bcp status) will be applied a suffix indicating if the current database version is backward compatible. _(e.g. - Database version: v0.6.1 (Backward Compatible))_ - Default SQLite database file name is now **logs.db**. (This change is backward compatible) ## Bug fixes - Fixed #9 - Fixed #12 - Fixed an issue not allowing inspector to getting logs of the replaced block. - Fixed crash during the rollback of entities. - Fixed possible issue with command permission check order. - Fixed order of plugin data folder creation. - Fixed wrong position calculation of liquid tracking. - Fixed correct meta value (damage) when placing block. - Fixed wrong restore of bed and doors when placed. - Fixed duplicated door log when breaking. - Fixed block burning rollback not correctly working some times. - Fixed purge command not correctly working on SQLite. - Fixed excessive log during inventory transaction. - Fixed database file creation on start-up not taking the choosed file name in the config. - Fixed possibles crashes relative to null values while tracking. - When rollback an area containing blocks with light source, the light will try to be updated. (This avoid empty light areas) - Don't log anymore players when they die. It causes a crash while rollback.
Issue description
Steps to reproduce the issue
OS and versions
Plugins
Crashdump, backtrace or other files
Extra
Tested on:
CPU's:
(I own WitherHosting and have alot of hardware)
Ram:
Included for reference to show they are not like 1 core garbage CPU or Ram setups I have not looked into the plugin but i would assume that it has something to do with a loop getting stuck. or a really rapid listener.
The text was updated successfully, but these errors were encountered: