development branch crashes when you close a profile with a standalone map widget

Bug #1667895 reported by Vadim Peretokin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mudlet
Confirmed
High
Unassigned

Bug Description

development branch crashes when you close a profile with a standalone map widget. Does not happen in 2.1 or the release_30 branch.

Revision history for this message
Vadim Peretokin (vperetokin) wrote :
Revision history for this message
Vadim Peretokin (vperetokin) wrote :
Revision history for this message
Vadim Peretokin (vperetokin) wrote :
Revision history for this message
Vadim Peretokin (vperetokin) wrote :

I've found the commit that narrows down to the problem using git bisect: 7d34308b46b48a4f4cc78894056906fb4417bc3f. The issue isn't in the commit itself though, rather, it exposes a problem: when you open the map as a stand-alone, not embedded, widget and close the profile, the widget for the corresponding map does not get closed as it should.

The right fix would be close the stand-alone map widget associated with the profile when the profile is closed.

Changed in mudlet:
milestone: none → trunk
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Stephen Lyons (slysven) wrote :

Could this be a duplicate of https://bugs.launchpad.net/mudlet/+bug/1229493? Each Host class instance is not cleaning up after itself properly by destroying any QDockWidget based dlgMapper/TMap/T2DMap/glWidget classes. For the normal single profile use case this is not apparent because the Application itself closes any remaining widgets (and if you run with the command line argument "--widgetcount" it will tell you **how many it had to clean up for you**...!) - at present though, if you are using any user/package created toolbars/menus/buttons there are other sources of uncleaned up widgets - but I'm working on that as I type...

Revision history for this message
Vadim Peretokin (vperetokin) wrote :

Yeah it is exactly a duplicate of that. Will mark it as such.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.