touch-packages team mailing list archive

Thread
Date

[Bug 1445418] Re: Surfaces are not properly released in CustomWindowManagement.state_change_requests_are_associated_with_correct_surface

To: touch-packages@xxxxxxxxxxxxxxxxxxx
From: Launchpad Bug Tracker <1445418@xxxxxxxxxxxxxxxxxx>
Date: Thu, 28 May 2015 04:44:04 -0000
Reply-to: Bug 1445418 <1445418@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Branch linked: lp:ubuntu/wily-proposed/mir

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1445418

Title:
  Surfaces are not properly released in
  CustomWindowManagement.state_change_requests_are_associated_with_correct_surface

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  New

Bug description:
  Memory leak in CustomWindowManagement,
  state_change_requests_are_associated_with_correct_surface is causing
  CI failures in unrelated tests.

  Seen in https://jenkins.qa.ubuntu.com/job/mir-vivid-
  amd64-ci/1537/consoleFull:

  7: ==13773== 1,359,533 (14,960 direct, 1,344,573 indirect) bytes in 17 blocks are definitely lost in loss record 127 of 127
  7: ==13773==    at 0x4C2C100: operator new(unsigned long) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  7: ==13773==    by 0x8E5C24: MirConnection::create_surface(MirSurfaceSpec const&, void (*)(MirSurface*, void*), void*) (mir_connection.cpp:147)
  7: ==13773==    by 0x8D682F: mir_surface_create (mir_surface_api.cpp:149)
  7: ==13773==    by 0x8D6A1A: mir_surface_create_sync (mir_surface_api.cpp:133)
  7: ==13773==    by 0x6D9FC7: (anonymous namespace)::Client::surface_create() const (test_custom_window_management.cpp:77)
  ...

  It's strange that the leak is not consistently detected by valgrind.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1445418/+subscriptions