Re: [Tracker] Memory usage for tracker-extract and tracker-miner-fs
- From: Joe Rhodes <lists joerhodes com>
- To: Carlos Garnacho <carlosg gnome org>
- Cc: Philip Van Hoof <philip codeminded be>, Tracker mailing list <tracker-list gnome org>
- Subject: Re: [Tracker] Memory usage for tracker-extract and tracker-miner-fs
- Date: Sun, 17 Jan 2016 20:02:15 -0500
Carlos:
I just tried the 1.7.2 tarball. I think we may still have a leak. The two processes were heading up over
600 MB's.
Here are the valgrind outputs. I hope this helps:
https://www.dropbox.com/s/gyndn7ithpge6nc/valgrind-tracker-extract-log-1.7.2.gz?dl=0
https://www.dropbox.com/s/h250z3lh9mvr2vv/valgrind-tracker-miner-fs-log-1.7.2.gz?dl=0
I'm fairly certain I had included this previously, but here's the output status of my "./configure" command:
Build Configuration:
Prefix: /usr/local
Source code location: .
Compiler: gcc
Compiler Warnings: no
C Flags:
VALA Flags: -Wno-unused-variable -Wno-unused-function -Wno-shadow
-Wno-format-nonliteral -Wno-sign-compare -Wno-strict-prototypes
Win32: no
Enable gtk doc (for documentation): no
Enable man pages for GSettings: yes
Enable functional tests: no
Enable unit tests: yes
Feature Support:
Support for HAL: no
Support for UPower: no
Support for network status detection: no
Unicode support library: libunistring
Build with Journal support: yes
Build with SQLite FTS support: yes (built-in FTS: yes)
Build with Stemming support: no
Cache media art no (libmediaart)
Install artwork yes
Bash completion support: yes (/usr/share/bash-completion/completions)
Data Miners / Writebacks:
FS (File System): yes (MeeGo support: no (disabled))
Applications: yes
RSS: no
User Guides: yes
Email:
Evolution: no (/dev/null)
Thunderbird: no (/dev/null)
Bookmarks:
FireFox: yes (NONE/lib/firefox-addons/extensions)
Extract (secondary extraction): yes
Writeback (writing changes back): yes
Metadata Extractors:
Support PNG: yes
Support PDF: no
Support XPS: no
Support GIF: no (xmp: no)
Support JPEG: yes (xmp: no, exif: no, iptc: no)
Support TIFF: yes (xmp: no, exif: yes, iptc: no)
Support Vorbis (ogg/etc): no (disabled)
Support Flac: no (disabled)
Support MS & Open Office: yes
Support XML / HTML: yes
Support embedded / sidecar XMP: no
Support generic media formats: ? (An external generic_media player will be called) (backend:
N/A)
Support cue sheet parsing: no
Support playlists (w/ Totem): no
Support ISO image parsing: no
Support AbiWord document parsing: yes
Support DVI parsing: yes
Support MP3 parsing: yes
Support MP3 tag charset detection: no (icu: , enca: no)
Support PS parsing: yes
Support text parsing: yes
Support icon parsing: yes
Writeback Formats:
Audio files using Taglib: no
XMP: no
Applications:
Build tracker-preferences: no
Build tracker-needle: no
Frameworks / Options:
Support GNOME's Nautilus no ()
Support Maemo no
Support libmeegotouch no (disabled)
Support Guaranteed Metadata no (e.g. guess nie:title from files)
Cheers!
-Joe
On Jan 17, 2016, at 4:00 PM, Carlos Garnacho <carlosg gnome org> wrote:
Hi Joe, Philip,
On Wed, Jan 13, 2016 at 8:55 AM, Philip Van Hoof <philip codeminded be> wrote:
Hi Joe,
Ok, that's fine. It would have been nice if we could let you do a
valgrind re-run of the same use-case to see if we catch all the memory
leaks before Carlos makes a new release.
But this way we'll do a post-release check of your use-case. If we see
more memory leaks after your retry we can always create a 7.1.3 release.
I'd say: Let the release horses go loose Carlos.
A bit later than hoped, but Tracker 1.7.2 is out :), with some further
last-minute leak fixes. It should run a lot better for you now Joe,
please let us know how it gets along.
Cheers,
Carlos
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]