knossos
knossos copied to clipboard
knossos-project
Viewports stop updating
This was triggered while zooming out. When this happens, i / o and mouse wheel zooming does not affect the XY viewport anymore and neither does moving in the dataset.
Just happened again, during zoom out (possibly exactly when crossing the mag boundary, not sure about this). Log since loading the last tracing:
[:0] Debug: QUrl( "file:///home/svara/work/mpi/Electron Microscopy/EM analysis/f0097 analysis/LVRD-Pre Analyis/re_tracet/lvr050_pre033/LVR050_Pre033.nml" )
[:0] Debug: loading skeleton took: 50
[:0] Debug: loading skeleton took: 17
[:0] Critical: no slots 5 124 0
[:0] Debug: loading skeleton took: 65
[:0] Critical: no slots 5 124 0
[:0] Debug: loading skeleton took: 5
[:0] Critical: no slots 5 124 0
[:0] Debug: selection hits: 5
[:0] Debug: selection hits: 7
[:0] Critical: no slots 5 124 0
[:0] Warning: QNetworkReplyImplPrivate::error: Internal problem, this method must only be called once.
[:0] Warning: QNetworkReplyImplPrivate::error: Internal problem, this method must only be called once.
[:0] Critical: no slots 5 124 0
[:0] Critical: no slots 5 124 0
[:0] Critical: no slots 5 124 0
[:0] Critical: no slots 5 124 0
[:0] Critical: no slots 5 124 0
[:0] Critical: no slots 5 124 0
[:0] Critical: no slots 5 124 0
[:0] Critical: no slots 5 124 0
[:0] Critical: no slots 5 124 0
[:0] Warning: QNetworkReplyImplPrivate::error: Internal problem, this method must only be called once.
[:0] Critical: no slots 5 124 0
[:0] Critical: no slots 5 124 0
[:0] Warning: QNetworkReplyImplPrivate::error: Internal problem, this method must only be called once.
[:0] Warning: QNetworkReplyImplPrivate::error: Internal problem, this method must only be called once.
[:0] Critical: no slots 5 124 0
[:0] Critical: no slots 5 124 0
[:0] Critical: no slots 5 124 0
[:0] Critical: no slots 5 124 0
[:0] Critical: no slots 5 124 0
The log is showing a problem, but missing cubes don’t explain why the viewport is unresponsive imo.
This happens very regularly and is extremely annoying. Any suggestions for specific revisions that may have had an influence, so that I can start a seach for the commit that introduced this? (It started happening only recently...)
If it happens regularly use a screen video capture so we know what has been done beforehand. Never happened to me so far. Possibly a hardware issue or OS specific?
I think i just experienced this. Maximizing and de-maximizing fixed it.
Possibly two different scenarios? Fabi's case looks like a memory corruption, or else there wouldn't be so many critical/assertions. While your case seems more transient (or do you also see these log messages?)
I assume the log is symptomatic to the deeper issue Fabi had, e.g. corruption, which might account for the other symptomatic update arrest. Unless "no slot" is still quite common nowadays.
That slots are missing is not a sign of memory corruption. the warnings from Qt are a known bug on their end.
AFAIK we should never miss a slot (wrongly stated Critical, this is in fact a simple assertion).
Right, but it just means that the managing logic is/was buggy (i assume so).
Or it means that the unbuggy logic works on corrupt data. Again, unless this assertion is quite common, even in the absence of other problems.