Changes between Initial Version and Version 1 of Ticket #20989, comment 7


Ignore:
Timestamp:
2021-07-13T22:56:10+02:00 (5 years ago)
Author:
Bjoeni

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #20989, comment 7

    initial v1  
    33Well I'm aware that this is the chain of events that is currently happening, however I think that at least some of the steps are unnecessary just before closing. I agree on the can of worms though.
    44
    5 So in that case the easiest solution would probably be to shutdown the worker after removing all layers (that still means that the next active layer is always set, which doesn't seem ideal to me but that's just status quo).
     5So in that case the easiest solution would probably be to shutdown the worker after removing all layers (that still means that a new active layer is set multiple times while closing, which doesn't seem ideal to me but that's just status quo).
    66
    77Or fixing it in the geoimage layer, basically making sure that all instances using the worker check if it's still alive.