-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Message schemaVersion
Index Migration Causes Out-Of-Memory Error
#2163
Comments
This was working fine earlier in the day with whatever version I was using before I dist-upgraded around noon. |
Also, to be a little clearer, Signal is now unusable for me on desktop as it crashes after about 9 minutes every time I load it up. |
Hi there, @rubin110. Thank you very much for being a Beta tester. You have saved many others the pain of going through what you're going through right now. To unblock daily usage, you might consider installing the production version, linking that up to your phone (the limit is five linked devices), and using it in the near term. Several questions:
|
Another Q: How big is your |
Another couple questions: can you tell us about your computer's specs? How much RAM? Processor speed? |
I see this same issue on startup with 1.7.0-beta2. ~/.config/Signal Beta/IndexedDB is 4.2 GB CPU: Intel(R) Xeon(R) CPU E3-1505M v5 @ 2.80GHz
|
It eats up about 6 gigs of real memory and 10 gigs of virtual memory before something chokes and it dies. Here's a screenshot of htop about 1 minute before it died... My machine is a ThinkPad X1 4th Gen, Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz, with 16gb of ram running Debian Sid with KDE Plasma 5.12.3.
For what it's worth |
I'm wondering if my issues around #2070 are related. Previously when I could load up Signal I would get the sense that some part of the UI for that conversation would lock up when I clicked on it, mostly happening with conversations that had a long long (multi year at this point) backlog. Occasionally some of those conversations would (after tens of seconds to a minute or two of churning) would get unstuck and display the messaging log with text field, but with no backlog. I'm thinking now what must have been happening was something part of a db getting loaded into memory (or paging taking too long) and the client finally giving up. |
@rubin110 One thing is for sure - you win the prize for the biggest data folder we've ever seen! And it is almost certainly causing problems across all the app as the app struggles with the size of all the data. We are working on it as we speak. |
Thanks for the prize, I'm honored! I blame the combination of being really good about backing up/persisting my data over the years, and the Bitmoji only group conversation I created last year. I'd like to thank my mom for having no idea how computers work, and @liliakai for insisting that Signal works perfectly fine for our group chat at Congress so many years ago. @scottnonnenberg-signal: I don't know if you're in the SF office, but if it would help having my laptop within glaring distance to debug this I'm happy to drop around late lunch today. |
schemaVersion
Index Migration Causes Out-Of-Memory Error
With Signal beta 1.7.0-beta.3 on Debian Sid, after about 5-10 minutes of churning by being stuck on the initial loading screen, the app loads fine and I can see my list of contacts and click into conversations with no problem or any sort of terrible delay. The process while loading didn't ever go over about 300mb of real memory or about 2.5gb of virtual. Currently idling at 225mb real, 1.86gb virtual. Quitting and loading the app for a second time, it only took about 30 seconds to open up and get to my list of conversations. Do note I did just upgrade to a ThinkPad T480s with 24GB of ram, but it looks like whatever change has happened with 1.7.0-beta.3, it hardly used any of that available memory. @mmirg: Do you also see this fix? If you do then I would consider this issue squashed. |
@rubin110 I meant to reach out proactively but alas. Glad your initial experience with the new beta build was positive! Our focus was to unblock people like you and incrementally improve performance and stability for everyone. We went back and forth between doing an upfront database optimization or do it in the background. Since it an upfront migration could have taken on the order of minutes, we opted for the background mechanism. This means the app should get faster and better over time. For the best experience, please leave the app open, even if not used. We appreciate your initial report as it helped us refine our approach and would appreciate any feedback regarding performance / stability (time to open conversation, memory usage, etc.) going forward, whether good or bad! |
@rubin110 I will close this issue as we believe the out-of-memory error on startup should have been resolved with the 1.7.0-beta.3 release. As I previously said, please continue sharing any valuable experiences / metrics going forward in this thread 😄 |
Bug description
After installing 1.7.0-beta.2, Signal shows loading triple throbber for a few minutes before process dies. While it attempts to load Signal eats up a substantial part of CPU.
Steps to reproduce
Actual result:
After some minimal loading time Signal opens to the conversation list screen.
Expected result:
After about 9 minutes of loading, Signal closes and disappears. No process is left over.
Screenshots
Platform info
Signal version:
1.7.0-beta.2
Operating System:
Debian Sid, Linux 4.15.0-1-amd64
Linked device version:
4.16.9
Link to debug log
Here's the tail end of a
signal-desktop-beta -vvvvv
:The text was updated successfully, but these errors were encountered: