Carsten Haubold

I can confirm these freezes. I'm also playing on an Intel based Mac, running BigSur. I haven't used OpenEmu for a while but I cannot remember those freezes happened with...

Probably this is the same issue as https://github.com/OpenEmu/OpenEmu/issues/4657

This is the debugger output, it looks like something happens deep inside Qt... ```GDB * thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=EXC_I386_GPFLT) frame #0: 0x00000001096398ef libQtCore.4.8.7.dylib`QMetaObject::changeGuard(QObject**, QObject*)...

The error occurs *after* all steps in `DataSelectionGui.addFiles(...)` have been processed, which is triggered by a user clicking `Add separate files...`. This includes handling a `DatasetConstraintError` due to an axes...

When running ilastik with the lazyflow threadpool disabled (`LAZYFLOW_NUM_THREADS=0`), the crash does not occur. This looks like it is indeed some invalid access to a Qt object from a non-GUI...

We're running into this error as well on different Windows machines behind corporate proxies. After trying the options mentioned here to no avail, I followed what @marc-wien said a while...

I tried this solution locally but it didn't resolve the issue. For me setting `CURLSSLOPT_NATIVE_CA` did not help 😞

Oh sorry I guess I should've been more specific about the error: it is supposed to show up only if you open some data that is not 5D and thus...

And for the problem you are seeing: I noticed that as well during our bug fixing day and solved it by presenting an error to the user if `x` or...

So, the fix from https://github.com/ilastik/ilastik/issues/1527 is in, my assumption about a missing submodule update is wrong. Unfortunately that means, there is some other way we can run into a situation...