-
Notifications
You must be signed in to change notification settings - Fork 12
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
[Question] How to view more of the conversation history #115
Comments
Uhh. That's weird, as you scroll down it should keep loading more and more until there isn't any more data. I'll have to check |
Okay, I have a little more info on this. It works as expected on my Mac client (but still stuck on the same 1/15/21 LS chat on Windows)
crash transcoder.txt Let me know if I should test anything further. |
jetsam memory crash.txt 2021-03-09_2-21_am.txt
|
Hmm, it looks like the jetsam crashes are normal |
Jetsam crashes are indeed normal most of the times, I override the memory limit manually. However, still, I can't give it infinite memory. If you are crashing towards the end of your conversations, I would assume that you're running out of memory on your device. Which actually should not happen unless you have a weird/buggy thread there? I can personally scroll throughout all my history (until 2017) on my macOS and Windows machines |
For the lag, did you update the tweak? I pushed some changes that should help with that as well |
Yes, I updated both the tweak and the client, and for general use, the lag is much better. This was just one instance in which I loaded lots of old messages in one chat, so then that one chat became laggy. I'll test later if chats that have many incoming and outgoing messages in a short amount of time are still affected. |
Any info on this with 0.7.0? |
On version 0.7.0, I can still only see fifty chats in my conversation history, this time going as far back as 2/26/21 |
I noticed that I can't see my entire message history in the WebMessage client. Is there a setting that I need to enable for this?
The text was updated successfully, but these errors were encountered: