Hmm pretty sure if is wrong. Without debug symbols it doesn't know what code is running and just has a good guess. A stack trace with symbols will show a completely different stack
On Fri., 19 Jul. 2019, 9:26 am Nyall Dawson, <[email protected]> wrote: > On Thu, 18 Jul 2019 at 16:52, Nathan Woodrow <[email protected]> wrote: > > > > Yeah, in this case, the stack trace is wrong because of the lack of > symbols. The symbols could be installed with QGIS at the increase of > package size but maybe we can do that for a while until we catch this issue. > > I don't think the trace *is* wrong here. The recurring source of these > issues is that long-lived objects which have QgsCoordinateTransform > members are being cleaned up AFTER QgsApplication::exitQgis, where the > proj library handling is gracefully cleaned up. After > QgsApplication::exitQgis NOTHING should be accessing coordinate > transforms. > > Actually I just had an idea for a potential workaround... let me see > if this works... > > Nyall >
_______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
