Repository navigation
A received message hangs bitmessage-qt, possibly an insecurity? #900
Description
I received the attached message, and whenever I would attempt to select it from the qt interface, the program would hang and consume 100% CPU. The only way I could recover is to kill the program, then run bitmessagemain.py with the -c option, and delete the message. It appears the contents of the program are a DOS program. Nevertheless, this could be an inseurity in bitmessage and should be looked at. I can assist in a debug session if necessary.
Re: rapidgator premium available at a discount.txt
Activity
kirkawolff commentedon Oct 20, 2016
There is a message floating around general2 noting this problem:
PeterSurda commentedon Oct 20, 2016
Thank you for the report, as you noticed yourself, this already has been reported, also what it triggers and a possible workaround. I'm working at a proper fix right now.
PeterSurda commentedon Oct 20, 2016
Can you test with 448ceaa (or later) if it still happens?
kirkawolff commentedon Oct 21, 2016
it has no apparent effect. problem still present.
Long message parsing fix
PeterSurda commentedon Oct 21, 2016
It looks like there were two separate issues, one with the renderer on windows, and one with the regexp parser. The first commit fixes the first one, the second one the second one. I can't reproduce the problem anymore, can you retry?
kirkawolff commentedon Oct 21, 2016
It only locks up for one second. I am able to delete the message from the UI now.
PeterSurda commentedon Oct 21, 2016
Excellent, I just have to make another commit for Windows compatibility once I finish debugging it, and then I can finally close the issue.
Freezing message parser fix #2
PeterSurda commentedon Oct 21, 2016
Works for me now both on linux and windows, I'm closing the ticket.