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

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:

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

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:

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

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

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

I'll try to have a closer look tomorrow. Ulrich Am 08.04.2017 um 20:04 schrieb Roman Lebedev: On Sat, Apr 8, 2017 at 6:23 PM, Ulrich Pegelow wrote: Strange things also happen here. All of a sudden darktable would hang during startup in the OpenCL init phase of my

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

On Sat, Apr 8, 2017 at 6:23 PM, Ulrich Pegelow wrote: > Strange things also happen here. All of a sudden darktable would hang during > startup in the OpenCL init phase of my AMD card (catalyst driver). > > I bisected the issue and found this: >

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

I found that clinfo also segfaulted. Further investigation showed that the amdgpu libs had been changed. Reinstalling the few required libs solved my issue. So I suspect that an OS upgrade clobbered them. I placed them in /lib64 rather than in

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

Strange things also happen here. All of a sudden darktable would hang during startup in the OpenCL init phase of my AMD card (catalyst driver). I bisected the issue and found this: 97085123a6c29bed86fc7795d527c95bd50a is the first bad commit commit 97085123a6c29bed86fc7795d527c95bd50a

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

Il 05/04/2017 22:36, Mark Heieis ha scritto: > > Yep, darktable opens fine with opencl disabled, so clearly an (amd > driver/lib?) opencl issue. > Then you should fill a bugreport on AMD support website, so that they can fix it

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

Yep, darktable opens fine with opencl disabled, so clearly an (amd driver/lib?) opencl issue. On 2017-04-05 13:01, Mark Heieis wrote: Yes, I found that clinfo seg faults as well. So not sure if it's with the AMD

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

Yes, I found that clinfo seg faults as well. So not sure if it's with the AMD libs, the open source driver piece or a kernel update that's making this happen. On 2017-04-05 12:42, Roman Lebedev wrote: On Wed, Apr 5, 2017

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

On Wed, Apr 5, 2017 at 10:29 PM, Mark Heieis wrote: > Hi There, > > Today, for some reason, darktable seg faults with the following. I used it > yesterday and it worked fine. I may have updated the OS after my last use > and could roll-back the update to check. Any thoughts? > >

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

Hi There, Today, for some reason, darktable seg faults with the following. I used it yesterday and it worked fine. I may have updated the OS after my last use and could roll-back the update to check. Any thoughts? Linux copernicus