Problem with updated QGIS3 port

[Malauch]

I used QGIS3 port version from 2017-12-27 and it worked quite well. I just update port (QGIS version from 2018-01-10) and I noticed very annoying problem that opening layer preferences windows and trying to close it (by clicking OK or Cancel) hangs QGIS completely. I think it is much more problem with QGIS itself then port but I just would like to confirm if it's happening only for my or in general on MacOS.

[gnw3]

I was able to open and close the preferences for a raster layer (taken from a NetCDF4 file) several times, but after closing prefs and trying to drag the layer in the window qgis3 crashed:

System Integrity Protection: enabled

Crashed Thread:        16  Thread (pooled)

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
abort() called
*** error for object 0x7fd152d920c0: pointer being freed was not allocated

[...]

Thread 16 Crashed:: Thread (pooled)
0   libsystem_kernel.dylib        	0x00007fff913e3f06 __pthread_kill + 10
1   libsystem_pthread.dylib       	0x00007fff8edfa4ec pthread_kill + 90
2   libsystem_c.dylib             	0x00007fff8a50d6df abort + 129
3   libsystem_malloc.dylib        	0x00007fff8f427041 free + 425
4   libhdf5.101.dylib             	0x000000011590ff7c H5FL__reg_gc_list + 56
5   libhdf5.101.dylib             	0x0000000115910266 H5FL_reg_free + 77
6   libhdf5.101.dylib             	0x00000001159c1f6d H5S_close + 341
7   libhdf5.101.dylib             	0x00000001158759ad H5A_free + 246
8   ???                           	0x06000000000015fb 0 + 432345564227573243
9   libgdal.20.dylib              	0x000000010dd8c169 HDF5CreateGroupObjs(long long, char const*, void*) + 1446
10  ???                           	0x00007fd15490a040 0 + 140537043656768

[Veence (Vincent)]

Sorry, I overlooked this. Yes, I have the same problem too. I reported it upstream, but it turns out no one in the development team works on Mac, so… it’s going to be a hassle to get it fixed. It could, however, be related to the mismatch between current Qt version (5.10) and PyQt (still 5.9).

I’ll keep you posted.

[Malauch]

Thank you for information. It is possible that it is something with Qt, PyQT or some other dependencies because it started occurring with many other bugs in the same time.

[Veence (Vincent)]

I’ve just committed both a PyQt5 update to 5.10 and a QGIS3 update to latest commit, but none of those solve the problem. I‘m aware this can be a pain in the neck, up to the point of rendering QGis almost unusable. Not sure what to do about it, will dig a bit further, time permitting. If you have any lead, I’ll take it.

[Malauch]

Veence, did you tried any new build of QGIS3? Is the problem still there?

[ryandesign (Ryan Carsten Schmidt)]

I've submitted an update to qgis3 @3.0.0 in #55906 but I haven't tested if this problem still exists.

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #55925.

[Veence (Vincent)]

Replying to ryandesign:

I've submitted an update to qgis3 @3.0.0 in #55906 but I haven't tested if this problem still exists.

Thanks Ryan, I was in vacation (mid-term vacation) and unfortunately, while I took my Air with me, I forgot the power supply, and so I couldn't really use it but for emergency things. That also means I had a lot to catch up with when I came back yesterday.

It’s fine, it works like a charm now. Thanks for updating!