qbittorrent crashed with SIGSEGV in TorrentFilesModel::updateFilesPriorities()

[M.C. Botha]

Started download when crash occured

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: qbittorrent 2.9.5-1
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic i686
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Mon Mar 12 19:53:13 2012
ExecutablePath: /usr/bin/qbittorrent
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111129.1)
ProcCmdline: qbittorrent
ProcEnviron:
 LANGUAGE=en_ZA:en
 LANG=en_ZA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x815b989 <_ZN17TorrentFilesModel21updateFilesPrioritiesERKSt6vectorIiSaIiEE+89>: mov (%eax,%ecx,4),%ebp
 PC (0x0815b989) ok
 source "(%eax,%ecx,4)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%ebp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: qbittorrent
StacktraceTop:
 TorrentFilesModel::updateFilesPriorities(std::vector<int, std::allocator<int> > const&) ()
 PropertiesWidget::loadDynamicData() ()
 ?? ()
 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
 QStackedWidget::currentChanged(int) () from /usr/lib/i386-linux-gnu/libQtGui.so.4
Title: qbittorrent crashed with SIGSEGV in TorrentFilesModel::updateFilesPriorities()
UpgradeStatus: Upgraded to precise on 2012-01-31 (41 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 TorrentFilesModel::updateFilesPriorities(std::vector<int, std::allocator<int> > const&) ()
 PropertiesWidget::loadDynamicData() ()
 PropertiesWidget::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) ()
 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /tmp/tmpIIYNUk/usr/lib/i386-linux-gnu/libQtCore.so.4
 QStackedWidget::currentChanged (this=0xa344f18, _t1=4) at .moc/release-shared/moc_qstackedwidget.cpp:145

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.