Hi,
When I save files (to JPEG @ 90 - 100% compression) my processor goes to 100% and stays there for several minutes or more!
My PC tower is Windows 7 with 6 GB RAM and a AMD A6-3600 CPU @ 2.10 gHz.
It uses Darktable 3.8.1
I’ve tried installing 4.8.1 on my Windows 10 laptop, and it does exactly the same thing!
My laptop is Windows 10 with 16GB RAM and an i5-4340M CPU @ 2.9 gHz.
Any ideas what’s going on here?
It’s making it impossible to use Darktable.
Thanks - DT
Usually when i see a spike in cpu usage while saving a file it turns out to be a hardware issue. Either a failing drive or drive controller.
Have you tried saving to another drive? Like an external harddrive or thumb drive? If so are the results the same?
On a machine with 6gb ram, that isn’t that surprising.
Is the Win 10 machine faster at exporting?
The tower saves to an external HDD, and the laptop saves to its internal SSD drive.
The laptop just took around half an hour to save a JPEG…!
Whatever it is, it doesn’t appear to be Darktable version related, nor RAM or OS related.
If it’s harware related, then it’s a bit of a coincidence that BOTH of my different computers are suffering from the exact same hardware / driver failure at the same time…
I’ve just tried saving a file from Darktable as a JPEG @ 93%, from the laptop to a USB drive, and it’s yet again locked up the processor @ 100% for 20 minutes…!?
I can’t work like this. 20+ minutes PER FILE…!
I’ve just tried an uncompressed TIFF file format, again exactly the same results:
100% CPU for 20-odd minutes.
I think I may have to start using a different program.
Such a shame as I have really been enjoying Darktable.
My other options are:
GIMP
RawTherapee
FastStone Image Viewer
But none of them gave me the crop guidelines of 1/3’s + centre, which I use all the time.
or there’s my clunky old Photoshop 5.5…!
Please provide a log file using -d common.
Hi g-man,
I’m not sure what you mean “log file using -d common”…?
Could you please elaborate?
Thanks - D
@Daf-T , see 1.1.1 in the manual, something like this -
1.1.1. darktable binary
This binary starts darktable with its GUI and full functionality; it is the standard way of using darktable.
darktable is called with the following command line parameters:
darktable [-d {all,cache,camctl,camsupport,control,dev,
fswatch,imageio,input,ioporder,lighttable,lua,masks,
memory,nan,opencl,params,perf,pwstorage,print,signal,sql,undo}]
[|]
[–version]
[–disable-opencl]
[–library ]
[–datadir ]
[–moduledir ]
[–tmpdir ]
[–configdir ]
[–cachedir ]
[–localedir ]
[–luacmd ]
[–noiseprofiles ]
[–conf =]
All parameters are optional; in most cases users will start darktable without any additional parameters in which case darktable uses suitable defaults.
-d
This option enables debug output to the terminal. There are several subsystems of darktable and debugging of each of them can be activated separately. You can use this option multiple times if you want debugging output of more than one subsystem.
The log file I eventually found is 0KB so I can’t upload it
The file path that link showed me I could not find.
The INetCache folder isn’t there when I search the Windows subfolder (hidden folders switched to Visible), yet when I search for the darktable-log file, the explorer shows it in that exact location… that doesn’t appear to exist via the folder tree view!?!
The CMD line doesn’t identify any of the suggestions, saying "darktable.exe isn’t
The CMD line doesn’t identify any of the suggestions, saying “darktable.exe-d is not recognised as an internal or external command, operable program or batch file”
Do I need to switch on error logging somehow, in order to create a darktable-log.txt file greater than 0KB…?
Like the instructions say, you need to type the path. You can’t click to it. I’m the new version of dt (5.0 next week), it will be in my documents.
cmd
path to darktable/bin/Darktable -d common
OK, it sounds like you know what you’re talking about.
But it still doesn’t quite make sense to me.
So I go to CMD line, and type in “path to darktable/bin/Darktable -d common”…?
Or do I go to file explorer and search for “darktable/bin/Darktable -d common”…?
Or is this “-d common” thing something different to the file path?
I think I’m still missing something in your explaination of this.
Sorry I’m not getting this quicker.
you can also try ART;
I don’t remember windows 7 too much, so let use the windows 10 machine.
Go to run and type CMD and enter
This will open up a terminal window for you type commands. We want to run the command “darktable -d common”. The -d common is a special flag that tells the system to record extra information in the log. That will help us figure out what the problem is.
But to run the command, we first need to navigate the folder that has darktable (aka file to path). It will be something like this:
Cd C:\Program files\darktable\bin
Then type darktable -d common and export a file. Then upload the log file that dt will create.
Why not first try the windows resource manager and see where you stand wrt memory before you export and then you can try your export and check your resources… use this with the DT log when you run that and together it should show if there is a massive bottle neck.
I tried what you said here.
I currently have darktable open / running.
After using the CMD window and typing
Cd C:\Program Files\darktable\bin
it comes up with
C:\Program Files\darktable\bin>
I then type in
darktable -d common
and it pauses, then says
“Sorry Darktable could not be started (database is locked)…”
then follows with suggestions how to resolve the issue
Should I close darktable and try this all again?
As we were communicating, darktable started to operate normally out of the blue.
I edited and saved several photos with no problem.
I then went and made supper and watched TV (hence time gap).
I came back and tried a new photo, but it’s now doing the same thing again, locking the processor @ 100% and taking 20 minutes to save a JPEG.
What on earth is going on…?!