Fix undefined behavior by calling on almost destroyed object

Authored by sandsmark on Mar 27 2020, 1:38 PM.

Description

Fix undefined behavior by calling on almost destroyed object

Because mView is in the process of being destroyed we shouldn't try to touch it too much.

Warning from ubsan:

runtime error: member call on address 0x606000118e80 which does not
point to an object of type 'QAbstractScrollArea'

Reviewed By: ngraham

Differential Revision: https://phabricator.kde.org/D28342

Details

Committed
sandsmarkApr 19 2020, 2:43 PM
Reviewer
ngraham
Differential Revision
D28342: Fix undefined behavior by calling on almost destroyed object
Parents
R260:24e881134a94: Fix leak of Rows in infocontextmanageritem
Branches
Unknown
Tags
Unknown