seg fault using sqlite3 module

Bug #1720691 reported by Kevin O'Gorman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python3-defaults (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I got a seg fault and core dump about 5 hours into a hand-coded merge of two databases.

WAL (write-ahead logging) was enabled, and the journal was about 500MB, so I tried again with periodic commits, and after about 20 hours its still going strong.

In any event, I regard a seg fault on any input at all by an interpreter or compiler to be a bug, and I'm reporting it as such.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: python3 3.5.1-3
ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
Uname: Linux 4.4.0-96-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Oct 1 14:35:51 2017
InstallationDate: Installed on 2016-08-08 (419 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: python3-defaults
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Kevin O'Gorman (kogorman-pacbell) wrote :
Revision history for this message
Kevin O'Gorman (kogorman-pacbell) wrote :

The machine is a Core i7 with 32 GB RAM. The swap space is also 32 GB. Nothing else was active during this run other than the usual daemons; some terminal and browser windows were open, but not in use.

The activity was all on a RAID which had at the time 2 TB free.

Revision history for this message
Matthias Klose (doko) wrote :

a reproducer should be included

Changed in python3-defaults (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.