-
Notifications
You must be signed in to change notification settings - Fork 37
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
TApplication.HandleException Access violation #2
Comments
This looks, to me, as if "something" happened, that particular note decided it needed to be saved and we ran into the same problem that caused the exception in #14. Thats won't happen again but what was the "something" that caused the shutdown in the first place ? Its particularly disturbing in that it lost a note. I was pretty sure thats not likely to happen anymore. One thing, I thought at one time I saw a note being saved on exit that had not been changed. Did not chase that up at the time, it could be related but is not the "something" that triggered off the problem. Interesting that you were not interacting with tomboy-ng at the time, once changed notes are saved, it really should be doing nothing ..... If you see it happen again, be interesting to dee what dmsg says, OOM killer is a (remote) possibility. |
Thanks for the explanation. I close it as unreproducible and possible duplicate of #14. |
Just hit the first crash with tomboy-ng in the background, without really working with it. Will see if it is reproducible.
About output: Build date 2017/11/26 TargetCPU i386 OS Linux
OS: debian stretch
Version: ea481bd
size: 32M
build command:
lazbuild --pcp=../../lazconf Tomboy_NG.lpi # lazconf contains environmentoptions.xml (automatically copied from /etc/lazarus/) and packagefiles.xml which links kcontrolsbase.lpk kcontrolslaz.lpk
Lazarus version: 1.8.0RC5
edit: oh and i found a note is missing, maybe it crashed trying to save it.
The text was updated successfully, but these errors were encountered: