-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
Crash because of big picture sent via SMS #2226
Comments
Relevant ANR evidence showing our process was eating CPU for >6s
Last logs from us before ANR
|
Thanks for the bug report @peter-sc, sorry you're running into this. It sounds like sometimes received MMS parts are classified as a text and displayed. Will look further into it. |
Might it be because of big picture size? Other messages from this contact, which were <100kb were displayed OK. |
this should now be resolved thanks to #2294, if you're still having this issue please check back in and the issue will be reopened, thanks! :) |
I received MMS with 2MB picture inside. The thread with this message is opening for about 2mins on 2-core CPU. Then the picture is displayed as encrypted text (no picture). After pressing on the message and trying to delete it, app crashes.
Other MMS messages, which were sent before of smaller size, were received and shown correctly.
Device: Xperia SP, running CM11, nightly 22-11-2014
Textsecure: 2.3.3 from Play store
The text was updated successfully, but these errors were encountered: