[Expired for python3-defaults (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: python3-defaults (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: python3-defaults (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671952
Title:
python program gets segmentation fault
To manage
I don't think I can do that. All signs point to a problem that is directly
related to the size of the journal. You don't want my 100GB database, and
I don't want to fool around finding a script that creates one from scratch
hoping it will trigger the same problem. If you can't work from a core
Please file a bug on the Python bug tracker (https://bugs.python.org/)
and provide a minimal script that reproduces a crash.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671952
Title:
python
I modified the code to issue commit() calls, which it had not been
doing. It ran to completion, having made over 3 million changes to the
database. Perhaps a really big journal does not work well? Even if so,
I would consider a segmentation fault a bug.
--
You received this bug notification
