YAM crash during sending e-mail

[jens-maus]

Originally by christoph.poelzl@rmsvideo.ch on 2015-12-15 08:11:37 +0100

---

Summary

YAM crashes quite often here during sending e-mail. This happens not always. A log is attached, the crash is at the end of the log. Would be great if this could be corrected because when this happens I need to reset the machine, everything gets blocked!

Steps to reproduce

1. Just send an e-mail
   2.

Expected results

Actual results

Regression

Notes

[jens-maus]

Originally by christoph.poelzl@rmsvideo.ch on 2015-12-15 08:12:22 +0100

---

Attachment added: log_15-12-15 (411.7 KiB)

[tboeckel]

Originally on 2015-12-15 09:24:21 +0100

---

Most probably this is the culprit:

0x1a383800 -> libs:amissl/amissl_v097g.library Hunk 0 Offset 0x000a8780
0x1a387d28 -> libs:amissl/amissl_v097g.library Hunk 0 Offset 0x000acca8

As long as AmiSSL trashes memory there is nothing we can do against this.

[jens-maus]

Originally by christoph.poelzl@rmsvideo.ch on 2015-12-16 05:53:42 +0100

---

Ohh, this is a shame because it does makes me problems, I need to write a lot of e-mails and often I get this crash. It seems that I need to use amissl because the e-mail server needs a secure connection... hmmm... is there really not other way to solve this problem?

[tboeckel]

Originally on 2015-12-16 07:35:02 +0100

---

Of course there is something that can be done: motivate some more developers to assist us finishing the new AmiSSL version.

The project is hosted here: https://github.com/jens-maus/amissl

[jens-maus]

Originally by christoph.poelzl@rmsvideo.ch on 2015-12-17 07:20:02 +0100

---

I talk about to the developers I know and perhaps there will be some positive answer.

[walkero-gr]

Everyone, is this something that still happens? To be honest, I use latest Yam on my OS4 system and I don't have that issue. Since there are a lot of updates in AmiSSL, and a new PR waiting #712 , is this something that needs to be investigated?

[Futaura]

It isn't an issue anymore - it was either fixed with the switch to AmiSSL v4 or in e46dc29 where I had pointed out InitAmiSSL() and CleanupAmiSSL() where not being used correctly (I cleaned this up a little further in #712).