-
-
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
BUG: Signal Stuck on Optimizing Application (1.15.0-Beta.7) #2581
Comments
I have the same issue. Starting signal from the shell gives me this (first start after installing the update):
Closing and reopening signal after this changed the error (this error now appears on every start):
Like @khashyarkh, I also don't have access to the real debug log (clicking View -> Debug Log does nothing) Signal version: Operating System: Linked device version: |
We'll get a fix out for this in the next beta. Thanks for being a beta tester! |
same issue on Windows 10. thx @scottnonnenberg Log:
|
This issue was resolved for me after I updated to |
is it already available via the auto-updater? |
For OSX and Windows, yes. Linux is in-process. |
Well done, now it reads a very large count of messages. In the console there are sometimes messages like the following: |
@0xnor0 Not necessarily. You could always enter a bug and include the entire log, and I could take a look. |
I seem to continue to have this problem on GNU/Linux with v1.15.0-beta.8. This is what I get on launch:
This is what is output when I try to capture the debug log: |
@mmirg It doesn't look like you've hit any errors yet in the SQLCipher migration. How long have you given it so far? Also, how long has this desktop installation been in use? |
@scottnonnenberg The desktop installation has been in use since the Chrome desktop client was in alpha and then imported soon after the standalone desktop client was released as a beta. My Signal Beta database is roughly 450 MB and I seem to have roughly 4.5 GB of attachments. I let the r8 run for roughly ten minutes. When I roll back to r6 the program reaches a usable state in less than five minutes. Should I try waiting longer? |
What's r6? Sounds like you're a really heavy user - about how many messages per day do you send and receive? Either way, we're currently working on a progress screen that will help people prepare people for a potential wait. How big is |
It seems I just didn't give it enough time. I tried updating and opening the database again and it eventually opened. It took over twenty minutes to open. CPU usage appeared to average around 50% according to htop for the first fifteen minutes that I carefully monitored progress. db.sqlite is 141.1 MiB. Hardware: Linux 4.17.10-gentoo #1 SMP Thu Jul 26 11:29:06 BST 2018 x86_64 Intel(R) Xeon(R) CPU E3-1505M v5 @ 2.80GHz GenuineIntel GNU/Linux 16 GB 2133MHz DDR4 RAM SM951 NVMe SAMSUNG 256GB |
@khashyarkh Can we close this? |
@scottnonnenberg-signal sure thing, i was able to auto-update. |
I hit this problem too. I am not (as far as I know) using a test version of the app. When it asks to update to a new version I say yes. "Optimizing application." I tried installing a new copy of the app from the main page, it's called signal-desktop-mac-1.22.0.zip, and I'm getting the same "optimizing application" message. Any help much appreciated. ;-) |
@scripting Commenting on closed issues is not going to help. Please enter a new bug and include a debug log. |
Bug description
Suddenly the update dialog came up, unpurposefully canceled the update dialog while typing, reopened the app and it's stuck on the Optimizing state.
Steps to reproduce
Actual result:
*There is no Access to Preferences to Delete Data.
*There is no Access to Submit Debug Log.
Expected result:
*More sophisticated update paradigm, possibly from preferences manually.
*Access to Preferences, Debug Log etc. in such cases.
Screenshots
Platform info
Signal version:
1.15.0-Beta.7
Operating System:
Windows 10
Linked device version:
2.28.0.15
The text was updated successfully, but these errors were encountered: