Bug#893057: python3-notmuch: random aborts on exit
David Bremnerwrites: > For what it's worth, I can't replicate that with the given script (I ran > it 1000 times without any aborts). I am not surprised, initially it worked fine for me too. No idea what changed. I ended up changing my script to use Python2. >> Curiously, changes to tags don't seem to be preserved after the program >> exits. This may or may not be related. > > Do you mean in the case that it aborts, or when it exits normally? Only when my script aborts after completion. -- Brian May
Bug#893057: python3-notmuch: random aborts on exit
Brian Maywrites: > On 2018-03-16 11:28, David Bremner wrote: > >> I suspect it has to do with changes in memory management in python3. >> >> You hide the problem by adding >> >> del(db) >> >> at the end of your script. > > Unfortunately, I still seem to be getting this abort error, although not > as often. For what it's worth, I can't replicate that with the given script (I ran it 1000 times without any aborts). > Curiously, changes to tags don't seem to be preserved after the program > exits. This may or may not be related. Do you mean in the case that it aborts, or when it exits normally?
Bug#893057: python3-notmuch: random aborts on exit
On 2018-03-16 11:28, David Bremner wrote: > I suspect it has to do with changes in memory management in python3. > > You hide the problem by adding > > del(db) > > at the end of your script. Unfortunately, I still seem to be getting this abort error, although not as often. Curiously, changes to tags don't seem to be preserved after the program exits. This may or may not be related.
Bug#893057: python3-notmuch: random aborts on exit
David Bremnerwrites: > You hide the problem by adding > > del(db) > > at the end of your script. > > You can read some discussion at > > https://notmuchmail.org/pipermail/notmuch/2016/021622.html Thanks for this, and the work around. The workaround works fine. -- Brian May
Bug#893057: python3-notmuch: random aborts on exit
Brian Maywrites: > === cut === > > I get the following output: > > brian@wspdigital:~$ /usr/bin/python3 ./tagmail > Aborted > > If I comment/remove any of the lines out (including the function that isn't > even referenced anywhere) or switch to Python2, then it works without any > problems. > > Am wondering if this is a Python3 bug. I suspect it has to do with changes in memory management in python3. You hide the problem by adding del(db) at the end of your script. You can read some discussion at https://notmuchmail.org/pipermail/notmuch/2016/021622.html
Bug#893057: python3-notmuch: random aborts on exit
On Fri, Mar 16 2018, Brian Maywrote: > If I try to run the following program on Debian Stretch: > > === cut === > #!/usr/bin/python3 > import notmuch > db = notmuch.Database(mode=notmuch.Database.MODE.READ_WRITE) > > def abcdef(): > pass > > q_new = notmuch.Query(db, 'tag:new') > === cut === > > I get the following output: > > brian@wspdigital:~$ /usr/bin/python3 ./tagmail > Aborted > > If I comment/remove any of the lines out (including the function that isn't > even referenced anywhere) or switch to Python2, then it works without any > problems. > > Am wondering if this is a Python3 bug. This is certainly very weird. I am able to reproduce. If I change the script to this, though, it works fine: #!/usr/bin/python3 import notmuch db = notmuch.Database(mode=notmuch.Database.MODE.READ_WRITE) q_new = notmuch.Query(db, 'tag:new') Something about the function definition in there causes this?? signature.asc Description: PGP signature
Bug#893057: python3-notmuch: random aborts on exit
Package: python3-notmuch Version: 0.23.7-3 Severity: important If I try to run the following program on Debian Stretch: === cut === #!/usr/bin/python3 import notmuch db = notmuch.Database(mode=notmuch.Database.MODE.READ_WRITE) def abcdef(): pass q_new = notmuch.Query(db, 'tag:new') === cut === I get the following output: brian@wspdigital:~$ /usr/bin/python3 ./tagmail Aborted If I comment/remove any of the lines out (including the function that isn't even referenced anywhere) or switch to Python2, then it works without any problems. Am wondering if this is a Python3 bug. -- System Information: Debian Release: 9.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-0.bpo.3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-notmuch depends on: ii libnotmuch4 0.23.7-3 ii python3 3.5.3-1 python3-notmuch recommends no packages. python3-notmuch suggests no packages. -- no debconf information