Skip to content
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

random crash with yam 2.10 (15.02.2018 #669

Open
MichaelMerkel opened this issue Mar 8, 2018 · 13 comments
Open

random crash with yam 2.10 (15.02.2018 #669

MichaelMerkel opened this issue Mar 8, 2018 · 13 comments

Comments

@MichaelMerkel
Copy link

@MichaelMerkel MichaelMerkel commented Mar 8, 2018

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?

@jens-maus
Copy link
Owner

@jens-maus jens-maus commented Mar 8, 2018

? more information please. Your ticket is incomplete.

@MichaelMerkel
Copy link
Author

@MichaelMerkel MichaelMerkel commented Mar 8, 2018

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

@MichaelMerkel
Copy link
Author

@MichaelMerkel MichaelMerkel commented Mar 8, 2018

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

@MichaelMerkel
Copy link
Author

@MichaelMerkel MichaelMerkel commented Mar 8, 2018

i just installed the new amissl update and codeset library.

@jens-maus
Copy link
Owner

@jens-maus jens-maus commented Mar 8, 2018

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

@jens-maus
Copy link
Owner

@jens-maus jens-maus commented Mar 8, 2018

@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.

@MichaelMerkel
Copy link
Author

@MichaelMerkel MichaelMerkel commented Mar 8, 2018

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

@MichaelMerkel
Copy link
Author

@MichaelMerkel MichaelMerkel commented Mar 8, 2018

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.

@jens-maus
Copy link
Owner

@jens-maus jens-maus commented Mar 8, 2018

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.

@tboeckel
Copy link
Collaborator

@tboeckel tboeckel commented Mar 8, 2018

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

@tboeckel
Copy link
Collaborator

@tboeckel tboeckel commented Mar 8, 2018

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.

@MichaelMerkel
Copy link
Author

@MichaelMerkel MichaelMerkel commented Mar 8, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants