-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Docker/Arch/Ubuntu: Cannot receive image attachment (out of memory) #3560
Comments
How do you install Signal Desktop? |
Using a dockerfile and
Install commands:
|
I do see a typo in there Something to look for when you next start the app is what is in the dev console - Also, please post complete logs next time you provide a debug log. Small sections don't give us the comprehensive picture we need of history and present state combined. |
I can't, because after the application crashes the developer tools panel disappears. If I insist several times it reopens but it is all blank because it has no source code.
This is the complete log and part of another (previous log). The application starts on the following line:
In the last (or penultimate) line the app fails. But the error is not related to the last line, it must be a thread that tries to load the image. |
Hello, After upgrading to version 1.27.3, I got more information:
The current dockerfile I use is:
PostData: This happens when I open an image (received) and change the window (another application). Then Signal freezes and closes. It seems that the problem of emojis no longer exists. |
That number doesn't seem very high. Perhaps you need to devote more RAM to that docker instance? Or your computer needs more RAM? Has Signal Desktop ever worked for you, by the way? |
My computer has 16GB of RAM. I have not set a limit to docker; it have access to all available ram memory.
Yes. The only problem has been and remains the images (sent or received). |
Do you run Chromium or Chrome on that machine? Have you tried starting the app with |
I have Google Chrome but I don't use it for privacy reasons. Now I tested signal with "--disable-gpu" and I have the same results: |
Steps to reproduce this issue:
My system: ArchLinux with a window manager i3wm. Signal desktop running on Ubuntu docker container. |
The reason to test Chromium's handling of images - Signal Desktop is based on Chromium technology. |
They are the consequence of not designing your own libraries and using third parties. (The nonsense of "not reinventing the wheel"). Signal has its own protocols, it should also have its own libraries. That way you don't depend on third parties. In Google there is chaos. Nothing works well. Not to mention the huge lack of privacy. |
More information: I send myself a picture from another smartphone. The message "DevTools was disconnected from the page." appears a second or two after the last 403 error. |
The scenario you describe is very simple: receiving a photo on Ubuntu Linux. We've tested that; it absolutely works. What we need you to do is track this down to the specific hardware/software/configuration causing it on your machine. Trying Chrome will help you do that. I'm going to leave this open, but it's very unlikely that a change on our side will fix this for you. |
Okay. But how I can do that? Have you tried Signal Desktop in a docker container on Linux and it works? Then I should try Chrome also in a docker container without Signal? So I think that something different does Signal and I have not seen the source code of Signal to know how it does. I'm very busy. It is probably some kernel 5.x configuration. ArchLinux always uses the latest kernel version and Debian users (Ubuntu, and others) take a long time to have it. Most do not even use Linux. If you tell me more precisely what I should try, I will. |
I've been watching this thread with interest, because I've been having a similar (but not identical) issue. I'm running Signal Desktop on Debian in a Docker container, and my host OS is Fedora. When I receive some (but not all) pictures, I get the Blue Screen. The only way to recover (that I know of) is to delete the contents of my To troubleshoot, I found two JPGs that, as far as I could tell, had identical encodings/JPG subversions. The only difference was that one was 400K and the other was 2M. The 400K JPG worked fine every time. The 2M JPG caused the Blue Screen every time. Further, I installed chromium (not chrome) in my Debian Docker container as @scottnonnenberg-signal suggested and ran it by modifying my After the above, I found that, 1) if I installed the chromium package and dependencies and 2) ran Thoughts. I doubt that the chromium package itself is what's important. I suspect it's one of its dependencies that I was missing. It pulls in many dependencies, though, and I haven't taken the time to research this further and figure out which were the crucial packages. More thoughts. I don't know if this will solve the problem @mvasi90 is having, but it has (apparently) solved mine. And I do feel like there's a clue here for @mvasi90's issue. |
@chiveturkey Install another +500MB of misery? The Signal desktop client could have 10MB, but how much does it really have? Much more and now are you saying that it works better with another half gigabyte. There is a lack of professionalism and qualified programmers here. |
@chiveturkey I'm not sure what type of black magic you're doing. +500MB in today's society is super expensive so on top of lacking professionalism you want us to waste our money also? Your fix to this solution isn't the fix I can't figure out so it's clearly wrong. |
@chiveturkey money? All a developer need is time, not money. Doing things right saves time on solutions. I'm wrong? Developing a good software without hundreds of problematic libraries has two benefits: save space and save third-party problems. (Without wasting your time as a developer and without wasting my time as a user and saving 90% of space on disk and RAM). I' wrong? The problem is that people always look for easy things and finish fast. As instance: Signal client can be 10MB and use 10% of current CPU and RAM usage. I am wrong? |
The forums are the right place for discussion, not Github Issues. You're notifying all watchers of this repo with every comment. https://community.signalusers.org/ |
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. |
This issue has been closed due to inactivity. |
Bug Description
Impossible to use Signal Desktop if images are sent or received. It does not matter if the images are photos or emojis. Even when I open the panel (the palette) of emojis, Signal crashes. The blue screen appears.
Steps to Reproduce
Actual Result:
Blue screen (formerly white screen).
Screenshots
Platform Info
Signal Version: Desktop v1.25.3
Operating System: Linux Distribution: Arch Linux, Kernel: 5.1.15 (Docker: Ubuntu 18.04)
Link to Debug Log
https://debuglogs.org/5228b003c99b79556c9598171debd25d8f5c06f3cc0e32df764082cb597fa49a
The text was updated successfully, but these errors were encountered: