Sync sqlite3 3.7.0-1.1 (main) from Debian unstable (main)

Bug #612370 reported by Chow Loong Jin
80
This bug affects 12 people
Affects Status Importance Assigned to Milestone
Banshee
Unknown
High
banshee (Debian)
Fix Released
Unknown
banshee (Ubuntu)
Invalid
Undecided
Unassigned
sqlite3 (Debian)
Fix Released
Unknown
sqlite3 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Hi,

For the rationale, please see the original description and discussion below.

Please sync sqlite3 3.7.0-1.1 from Debian unstable (main)

Changelog since 3.7.0:

sqlite3 (3.7.0-1.1) unstable; urgency=high

  [ Iain Lane ]
  * Non-maintainer upload.
  * Backport fix from upstream bug 13f033c865 to fix performance
    regression introduced in 3.7.0-1. (Closes: #591298)

  [ Julien Cristau ]
  * High urgency upload for RC bugfix.

 -- Julien Cristau <email address hidden> Sat, 07 Aug 2010 16:55:51 -0400

Cheers,
Iain

-- Original description follows --

  affects ubuntu/banshee
  status confirmed
  affects ubuntu/sqlite3
  status new
  subscribe tsmithe

[This is a transplanted Debian bug, that also applies to Ubuntu]
[Not sure whether this is a Banshee or SQLite bug.]

After I upgraded sqlite3 (and its libs) from 3.6.23.1-4 to 3.7.0-1, Banshee
becomes extremely slow. For instance, it hangs for a minute right after
startup, and also for many seconds in between songs. Fwiw, strace(1)'ing the
process shows nothing special.

Downgrading SQLite and its libs to the old version fixes the problem. Note
that the problem occurs with both Banshee 1.6.x and 1.7.x.

Attached is a log of banshee --debug --debug-sql which shows the SQL queries
performed, and the time taken for each one.

Tags: maverick
Revision history for this message
Chow Loong Jin (hyperair) wrote : Fwd: [pkg-cli-apps-team] Bug#591298: Banshee becomes extremely slow after sqlite3 3.6.23.1-4 => 3.7.0-1 upgrade
  • log Edit (257.2 KiB, text/plain; name="log")
summary: - Fwd: [pkg-cli-apps-team] Bug#591298: Banshee becomes extremely slow
- after sqlite3 3.6.23.1-4 => 3.7.0-1 upgrade
+ Banshee becomes extremely slow after sqlite3 3.6.23.1-4 => 3.7.0-1
+ upgrade
Changed in banshee (Debian):
status: Unknown → New
Changed in sqlite3 (Debian):
status: Unknown → New
Changed in banshee:
status: Unknown → New
Revision history for this message
wouter bolsterlee (wbolster) wrote : Re: Banshee becomes extremely slow after sqlite3 3.6.23.1-4 => 3.7.0-1 upgrade
Changed in banshee (Debian):
status: New → Confirmed
Changed in sqlite3 (Debian):
status: New → Confirmed
Changed in banshee:
status: New → Confirmed
Changed in sqlite3 (Ubuntu):
status: New → Triaged
Revision history for this message
Iain Lane (laney) wrote : Re: Bug#591298: regarding SQLite3 3.7.0 slowness with banshee

tags 591298 + fixed-upstream
forwarded 591298 http://www.sqlite.org/src/info/13f033c865f878
thanks

Hello,

[ ccing the Launchpad report too ]

On Wed, Aug 04, 2010 at 06:29:43PM +0100, Iain Lane wrote:
>Hiya,
>
>On Wed, Aug 04, 2010 at 06:40:39PM +0200, Laszlo Boszormenyi wrote:
>>Hi Iain,
>>
>>On Wed, 2010-08-04 at 17:20 +0100, Iain Lane wrote:
>>>forwarded 519298 http://article.gmane.org/gmane.comp.db.sqlite.general/58588
>>I've read that 3.7.0.1 won't contain the fix for this bug. Still,
>>reading the commits[1]:
>>[5074b85967] Update the version number to 3.7.0.1. (user: drh, tags: branch-3.7.0)
>>[3f367fe00e] Backport fix 267492d3a7eff7b for the performance regression caused by automatic indexing and reported by ticket 8011086c85c6c4040. (user: drh, tags: branch-3.7.0)
>>
>>Ticket 8011086c85c6c4040 seems to be your bugreport[2] and it said to be
>>backported to the 3.7.0 branch and targeted at 3.7.0.1 .
>>
>>>I also reproduced it using HEAD,
>>>and upstream also confirms that it's still present.
>>Strange, are you sure you've commit 3f367fe00e [3] in your tree?
>
>That's the ticket that drh had me test, and yes I do have that commit
>in my tree. Bug is still present regardless. See the URLs present in
>my mail to the upstream list (for reference, they are [0]) if you wish
>to reproduce for yourself. :)

This has now been fixed upstream. Here's the bug:

      http://www.sqlite.org/src/info/13f033c865f878

Would you like to backport the fix (presumably after updating to
3.7.0.1)? I will prepare the patch if so.

Cheers,
Iain

papukaija (papukaija)
tags: added: maverick
Changed in banshee:
status: Confirmed → Invalid
Revision history for this message
Harry (harry33) wrote : Re: Banshee becomes extremely slow after sqlite3 3.6.23.1-4 => 3.7.0-1 upgrade

The bug in sqlite3-0 has now been fixed upstream.
Released in debian as libsqlite3-0_3.7.0-1.1
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591298

Revision history for this message
Iain Lane (laney) wrote :

Yes, that was my NMU. I've asked for sponsorship for the sync now. Should be fixed soon.

Changed in banshee (Ubuntu):
status: Confirmed → Invalid
Changed in sqlite3 (Ubuntu):
status: Triaged → New
summary: - Banshee becomes extremely slow after sqlite3 3.6.23.1-4 => 3.7.0-1
- upgrade
+ Sync sqlite3 3.7.0-1.1 (main) from Debian unstable (main)
description: updated
Benjamin Drung (bdrung)
Changed in banshee:
assignee: nobody → Benjamin Drung (bdrung)
Benjamin Drung (bdrung)
Changed in banshee:
assignee: Benjamin Drung (bdrung) → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package sqlite3 - 3.7.0-1.1

---------------
sqlite3 (3.7.0-1.1) unstable; urgency=high

  [ Iain Lane ]
  * Non-maintainer upload.
  * Backport fix from upstream bug 13f033c865 to fix performance
    regression introduced in 3.7.0-1. (Closes: #591298)

  [ Julien Cristau ]
  * High urgency upload for RC bugfix.
 -- Chow Loong Jin <email address hidden> Sat, 07 Aug 2010 16:55:51 -0400

Changed in sqlite3 (Ubuntu):
status: New → Fix Released
Revision history for this message
Aleksander Morgado (aleksander-m) wrote :

SQLite 3.7.1 got released yesterday. For early testers, I prepared Lucid packages in my PPA already:
https://launchpad.net/~aleksander-m/+archive/sqlite3

Cheers.

Revision history for this message
Jeff (jdorenbush) wrote :

@Aleksander, the sqlite3 update seems to have helped.

...But I didn't have much time to move around my playlist to fully test it out because Banshee locked up. I ran it in debug mode and it looks like when trying to detect BMPs it freezes. It looks like it was able to detect the BMP of 5 songs and then it locked up.

Changed in banshee:
importance: Unknown → High
status: Invalid → Unknown
Changed in banshee (Debian):
status: Confirmed → Fix Released
Changed in sqlite3 (Debian):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

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