yam icon indicating copy to clipboard operation
yam copied to clipboard

random crash with yam 2.10 (15.02.2018

Open MichaelMerkel opened this issue 6 years ago • 13 comments

Submission type

  • Bug report

YAM version

2.10 (15.02.2018)

Used operating system

  • AmigaOS4/PPC

Used Amiga system

X1000

Unexpected behaviour you saw

GrimReaper when fetching mails in background

Steps to reproduce the problem

random crash?

MichaelMerkel avatar Mar 08 '18 07:03 MichaelMerkel

? more information please. Your ticket is incomplete.

jens-maus avatar Mar 08 '18 07:03 jens-maus

sorry - odysses just saved - and does not let me edit. just connected via my pc. uploading crashlog

MichaelMerkel avatar Mar 08 '18 07:03 MichaelMerkel

i have no idea if this helps... but i cannot provide much more than the grim reaper log.

MichaelMerkel avatar Mar 08 '18 07:03 MichaelMerkel

i just installed the new amissl update and codeset library.

MichaelMerkel avatar Mar 08 '18 07:03 MichaelMerkel

Please try the latest nightly build (2018-03-07) first.

jens-maus avatar Mar 08 '18 08:03 jens-maus

@tboeckel Can you reproduce the problem by trying to actually fetch emails with AmiSSL 4.2 in use?

@MichaelMerkel If the latest YAM nightly doesn't solve the issue please downgrade to AmiSSL 4.1 and report if this fixes the issues.

jens-maus avatar Mar 08 '18 08:03 jens-maus

Uh? Yam tells me there is no update available when checking? (also autocheck is on). Ok - downloading it manually now.

MichaelMerkel avatar Mar 08 '18 08:03 MichaelMerkel

well, i think the problem is, that is was quite random. i mean i manually fetched mails before. no problem. only after some 20 minutes or so the crash occured. let's see if i get this again.

MichaelMerkel avatar Mar 08 '18 08:03 MichaelMerkel

Do you have two or more mail providers configured? It seems that this might be caused because YAM is fetching from more than one mail server in parallel.

jens-maus avatar Mar 08 '18 08:03 jens-maus

So far I did single-threaded downloads only and these were working perfectly. I'll try parallel downloads as soon as possible.

tboeckel avatar Mar 08 '18 15:03 tboeckel

For me the crash looks like a trashed memory pool: [free.c:25] libs:amissl/amissl_v110g.library:free()+0x6c (section 1 @ 0x2179F8) line 25 of free.c is the FreePooled() call, but the real crash happens inside that function. Since the pointer to be freed has been confirmed to be non-NULL before already only the memory pool can be in an invalid state.

tboeckel avatar Mar 08 '18 15:03 tboeckel

yes. i have 5 providers active. i also see very often that, when manually checking all servers at once, i often get an ssl error for one of them. trying it again immediately afterwards it usully succeeds. sometimes getting an error from another provider. but again this works with the next try.

MichaelMerkel avatar Mar 08 '18 18:03 MichaelMerkel