I've committed a change to trunk that fixes this with my data set. (There might still be a brief spike, but it should take far less time.) I'm curious if you two (and anyone else seeing this problem) still have it with the latest revision.
-- Jim On Tue, Aug 10, 2010 at 1:52 PM, Martin Olsson <[email protected]> wrote: > FWIW, I can also repro this problem using on r2042 (I didn't bisect yet but > I can do it later if you really need it). > > Attached are some sampled stacks when a single core is pegged at 100%. I > had 133GB of JPGs and NEFs imported > (approx 26K files total). On a previous revision I also had CPU pegged > immediately after import of this > huge dir but that CPU hogging had other stacks and it stopped after a few > hours so I have had no pegged CPU > issues with shotwell for some time before I "svn up" recently. > > > Martin > > > > > > On 08/09/2010 11:11 PM, Jim Nelson wrote: > >> One more thing that could help us out, Peter. If you run Shotwell like >> this >> from the console: >> >> % gdb shotwell 2>&1 | tee ~/shotwell.trace >> >> Then type "run" at the gdb prompt to start Shotwell. When the CPU is >> pegged, type Ctrl+C (in the console, not in Shotwell) and type "bt full" >> at >> the gdb prompt. Then type "c" and exit Shotwell. >> >> If you could send us ~/shotwell.trace, that would be of great help as >> well. >> >> Thanks, >> >> -- Jim >> >> On Mon, Aug 9, 2010 at 1:44 PM, Peter DO Smith<[email protected]> >> wrote: >> >> Jim, my photos folder contains 10,229 jpeg photos and nearly an equal >>> number of RAW photos (.PEF and .DNG). There are 256 folders, each >>> containing >>> a sub-folder for the RAW photos. >>> >>> I will send the shotwell.log file to you tomorrow when I return to my >>> office. >>> Peter >>> >>> >>> On Mon, Aug 9, 2010 at 10:08 PM, Jim Nelson<[email protected]> wrote: >>> >>> Peter, >>>> >>>> Is your Pictures directory (i.e. your library directory, which you can >>>> determine from the Preferences dialog) rather large? I'm curious how >>>> many >>>> directories and files it might contain. >>>> >>>> If you could run Shotwell, let it go for a while (at 99.9% load) and >>>> then >>>> send me this file, that would help as well: >>>> >>>> ~/.cache/shotwell/shotwell.log >>>> >>>> -- Jim >>>> >>>> On Mon, Aug 9, 2010 at 11:48 AM, Peter DO Smith<[email protected] >>>> >wrote: >>>> >>>> I have been downloading and building from trunk every few days. >>>>> Todays download (2032) builds normally but after start up becomes >>>>> unresponsive and one of the CPUs is driven into 99.9% load. So I have >>>>> reverted to the previous version which runs fine. >>>>> I am using Ubuntu 10.04. I hope this report is useful to you. >>>>> Peter >>>>> _______________________________________________ >>>>> Shotwell mailing list >>>>> [email protected] >>>>> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >>>>> >>>>> >>>> >>>> >>> _______________________________________________ >> Shotwell mailing list >> [email protected] >> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >> >> > _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
