-
Notifications
You must be signed in to change notification settings - Fork 55
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
Log entries are randomly truncated, omitted or merged #46
Comments
yes, I found this bug, I'm trying to fix it. |
Related to #43. |
Just tried out MCLog because filtering would be an incredibly helpful feature to have; however, I'm seeing this issue as well. Even with no active filtering (empty search box) the full console output had some missing logs and some "lumped together" (no newline between logs). My results were consistent; the same logs would have the same issues every time, and all issues disappeared after uninstalling MCLog. |
If this is a regex problem, I could solve it easily (disclaimer: I ❤️ regex) but I don't understand the code to know where to look. |
Sorry for that which makes you suffered this terribly. I'm still looking for the answer. Hopefully, @alexlee002 can find out the problem. |
I couldn't reproduce the issue every time, but it did happen. Maybe there is a bug in where MCLog separate the buffer into several log items. I will try to fix it. |
I am using MCLog with Xcode Version 7.2.1 (7C1002).
I noticed that sometimes (no idea what the pattern is) log entries are truncated, e.g. only the last 20-30 characters appear, some are omitted (breakpoint hits the logging statement, but no log entry appears), some are lumped together and appear in the same line.
At first I thought CocoaLumberjack was the problem (it uses asynchronous logging), but when I switched to NSLog, it did not help.
This problem appears quite often (both with and without filtering active) and makes using MCLog impossible. It would be nice if it could be fixed since log filtering is a very useful feature.
The text was updated successfully, but these errors were encountered: