Re: [darktable-dev] OpenCL scheduling profiles

2017-04-09 Thread Matthias Andree
Am 09.04.2017 um 18:38 schrieb Ulrich Pegelow: > Am 09.04.2017 um 17:29 schrieb Matthias Andree: >>> What's your number of background threads (fourth entry in core >>> options)? >> >> It's currently set to 2, and if removed from the configuration file with >> darktable stopped, >> will revert to 2

Re: [darktable-dev] OpenCL scheduling profiles

2017-04-09 Thread Ulrich Pegelow
Am 09.04.2017 um 17:29 schrieb Matthias Andree: What's your number of background threads (fourth entry in core options)? It's currently set to 2, and if removed from the configuration file with darktable stopped, will revert to 2 when darktable gets restarted and closed next time. Note I see t

Re: [darktable-dev] OpenCL scheduling profiles

2017-04-09 Thread Matthias Andree
Am 09.04.2017 um 16:38 schrieb Ulrich Pegelow: > Am 09.04.2017 um 11:00 schrieb Matthias Andree: >> Am 08.04.2017 um 14:29 schrieb Ulrich Pegelow: >> 2. What bothers me though are the timeouts and their defaults. In >> practice, the darktable works ok-ish, but the lighttable does not. When >> a tru

Re: [darktable-dev] All of a sudden, darktable Thread Seg faults

2017-04-09 Thread Ulrich Pegelow
Thanks. Works here. Let's see if his also fixes the SegFault reported by the TO. Ulrich Am 09.04.2017 um 16:49 schrieb Roman Lebedev: And, pushed. ___ darktable developer mailing list to unsubscribe send a mail to darkta

Re: [darktable-dev] All of a sudden, darktable Thread Seg faults

2017-04-09 Thread Roman Lebedev
On Sun, Apr 9, 2017 at 3:43 PM, Ulrich Pegelow wrote: > Am 09.04.2017 um 09:31 schrieb Roman Lebedev: >> >> On Sun, Apr 9, 2017 at 9:59 AM, Ulrich Pegelow >> wrote: >>> >>> Am 08.04.2017 um 20:04 schrieb Roman Lebedev: Well, that is *very* strange indeed. If it *reliably* happ

Re: [darktable-dev] OpenCL scheduling profiles

2017-04-09 Thread Ulrich Pegelow
Am 09.04.2017 um 11:00 schrieb Matthias Andree: Am 08.04.2017 um 14:29 schrieb Ulrich Pegelow: 2. What bothers me though are the timeouts and their defaults. In practice, the darktable works ok-ish, but the lighttable does not. When a truckload full of small thumbnails (say, lighttable zoomed out

Re: [darktable-dev] All of a sudden, darktable Thread Seg faults

2017-04-09 Thread Roman Lebedev
On Sun, Apr 9, 2017 at 3:43 PM, Ulrich Pegelow wrote: > Am 09.04.2017 um 09:31 schrieb Roman Lebedev: >> >> On Sun, Apr 9, 2017 at 9:59 AM, Ulrich Pegelow >> wrote: >>> >>> Am 08.04.2017 um 20:04 schrieb Roman Lebedev: Well, that is *very* strange indeed. If it *reliably* happ

Re: [darktable-dev] All of a sudden, darktable Thread Seg faults

2017-04-09 Thread Ulrich Pegelow
Am 09.04.2017 um 09:31 schrieb Roman Lebedev: On Sun, Apr 9, 2017 at 9:59 AM, Ulrich Pegelow wrote: Am 08.04.2017 um 20:04 schrieb Roman Lebedev: Well, that is *very* strange indeed. If it *reliably* happens for you, then maybe you could also bisect this within the submodule itself? Very c

Re: [darktable-dev] OpenCL scheduling profiles

2017-04-09 Thread Matthias Andree
Am 08.04.2017 um 14:29 schrieb Ulrich Pegelow: > Hi, > > I added a bit more flexibility concerning OpenCL device scheduling > into master. There is a new selection box in preferences (core > options) that allows to choose among a few typical presets. > > The main target are modern systems with very

Re: [darktable-dev] All of a sudden, darktable Thread Seg faults

2017-04-09 Thread Ulrich Pegelow
Am 09.04.2017 um 09:31 schrieb Roman Lebedev: On Sun, Apr 9, 2017 at 9:59 AM, Ulrich Pegelow wrote: Am 08.04.2017 um 20:04 schrieb Roman Lebedev: Well, that is *very* strange indeed. If it *reliably* happens for you, then maybe you could also bisect this within the submodule itself? Very c

Re: [darktable-dev] All of a sudden, darktable Thread Seg faults

2017-04-09 Thread Roman Lebedev
On Sun, Apr 9, 2017 at 9:59 AM, Ulrich Pegelow wrote: > Am 08.04.2017 um 20:04 schrieb Roman Lebedev: >> >> Well, that is *very* strange indeed. >> If it *reliably* happens for you, then maybe you could also bisect this >> within the submodule itself? >> > > Very clear result: Aha, now that makes

Re: [darktable-dev] All of a sudden, darktable Thread Seg faults

2017-04-09 Thread Ulrich Pegelow
Am 08.04.2017 um 20:04 schrieb Roman Lebedev: Well, that is *very* strange indeed. If it *reliably* happens for you, then maybe you could also bisect this within the submodule itself? Very clear result: 7f087325d09e2b6d4ecc392f7aee44dd29fafe62 is the first bad commit commit 7f087325d09e2b6d4e