-
Notifications
You must be signed in to change notification settings - Fork 498
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
Large log file #48
Comments
I'm not sure what could be causing this error. In the next release, I'll make this error log the file/directory that TabNIne was looking for. I don't support TabNine was indexing the log file? This can easily lead to log file blowup. |
@zxqfl I'm not sure. Is it possible that opening the said file in vim would cause it to be indexed? I don't think I ever looked at the log, and the first time I went to seek it out it was already ~1GB. Including file/directory in the log statement sounds like a good idea so next time this has some extra context. |
I'm seeing the same log messages being spammed, as well as CPUs being maxed out for minutes at a time.
|
Does it still reproduce? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Moving tbodt/deoplete-tabnine#18 to the appropriate place.
The log appears to be out of control:
It seems to be mostly polluted by the following message:
I'm not sure if it's related to the CPU usage problems, but TabNine has been spiking to 200-300% cpu util without any apparent need (in fact often vim is actually suspended through C-Z).
Potentially related to #24?
The text was updated successfully, but these errors were encountered: