date:20180220

[Bug 1316970] Re: g_dbus memory leak in lrmd

2018-02-20 Thread Seyeong Kim

** Description changed:

  [Impact]
  lrmd daemon with upstart resource has memory leak in Trusty
  
  affected to pacemaker 1.1.10.
- affected to glib2.0 2.40.2-0ubuntu1
+ affected to glib2.0 2.40.2-0ubuntu1 >> for glib2.0 created new lp [3]
  
  Please note that patch for pacemaker is created myself.
  
  [Test Case]
  
- 1. deploy 3 trusty instance.
- 2. install corosync, pacemaker, mysql.
- 3. setting with below info
- 3.1 corosync.conf, proper setting for 3 node
- 3.2 crm configure < setup.crm ( which has upstart:mysql setting )
- 3.3 monitor lrmd daemon's memory usage
+ https://pastebin.ubuntu.com/p/fqK6Cx3SKK/
+ you can check memory leak with this script
  
  [Regression]
- Restarting daemon after upgrading this pkg will be needed. this patch added 
NULL check for several parts. prior commit[1] changed file structure. and This 
change makes user changes usage of upstart:mysql to lsb:mysql. So I added free 
function myself. This might affect to system.
- For glib2.0, commit [1] is critical, but [2],[3],[4] is needed for building 
it.
+ Restarting daemon after upgrading this pkg will be needed. this patch adds 
free for non-freed dynamic allocated memory. so it solves memory leak. 
  
  [Others]
  
- Related commits.
+ this patch is from my self with testing.
  
- [1] commit a7b61e276120184c7586a3217ed3571a982f5017
- Author: Andrew Beekhof 
- Date:   Fri Aug 23 16:25:35 2013 +1000
- 
- Refactor: attrd: Move to its own directory and create a stub for
- attrd-ng
- 
- --
- $ git describe --contains a1a6922e43dfe80b23887a88401cbb93fe3645c0
- Pacemaker-1.1.11-rc3
- 
- $ git describe --contains a7b61e276120184c7586a3217ed3571a982f5017
- Pacemaker-1.1.11-rc1~168
- 
- $ rmadison pacemaker
-  pacemaker | 1.1.10+git20130802-1ubuntu2   | trusty
-  pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-security
-  pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-updates
- 
-  pacemaker | 1.1.14-2ubuntu1   | xenial
-  pacemaker | 1.1.14-2ubuntu1.3 | xenial-security
-  pacemaker | 1.1.14-2ubuntu1.3 | xenial-update
-  pacemaker | 1.1.16-1ubuntu1   | zesty
-  pacemaker | 1.1.16-1ubuntu1   | artful
-  pacemaker | 1.1.18~rc3-1ubuntu1   | bionic
- --
- 
- For glib
- [1] 
https://github.com/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c
- [2] 
https://github.com/GNOME/glib/commit/8792609e15394967cab526838b83f90acb401663
- [3] 
https://github.com/GNOME/glib/commit/ec02a1875f29ecb8e46c0d8c1403cd00a0b3a9e4
- [4] 
https://github.com/GNOME/glib/commit/f10b6550ff2ce55d06b92d6dc3e443fc007b2f7a
+ Please review carefully if it is ok.
  
  [Original Description]
  
  I'm running Pacemaker 1.1.10+git20130802-1ubuntu1 on Ubuntu Saucy
  (13.10) and have encountered a memory leak in lrmd.
  
  The details of the bug are covered here in this thread
  (http://oss.clusterlabs.org/pipermail/pacemaker/2014-May/021689.html)
  but to summarise, the Pacemaker developers believe the leak is caused by
  the g_dbus API, the use of which was removed in Pacemaker 1.11.
  
  I've also attached the Valgrind output from the run that exposed the
  issue.
  
  Given that this issue affects production stability (a periodic restart
  of Pacemaker is required), will a version of 1.11 be released for
  Trusty? (I'm happy to upgrade the OS to Trusty to get it).
  
  If not, can you advise which version of the OS will be the first to take
  1.11 please?

** Description changed:

  [Impact]
  lrmd daemon with upstart resource has memory leak in Trusty
  
  affected to pacemaker 1.1.10.
- affected to glib2.0 2.40.2-0ubuntu1 >> for glib2.0 created new lp [3]
+ affected to glib2.0 2.40.2-0ubuntu1 >> for glib2.0 created new lp [1]
  
  Please note that patch for pacemaker is created myself.
  
  [Test Case]
  
  https://pastebin.ubuntu.com/p/fqK6Cx3SKK/
  you can check memory leak with this script
  
  [Regression]
- Restarting daemon after upgrading this pkg will be needed. this patch adds 
free for non-freed dynamic allocated memory. so it solves memory leak. 
+ Restarting daemon after upgrading this pkg will be needed. this patch adds 
free for non-freed dynamic allocated memory. so it solves memory leak.
  
  [Others]
  
  this patch is from my self with testing.
  
  Please review carefully if it is ok.
+ 
+ [1] https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1750741
  
  [Original Description]
  
  I'm running Pacemaker 1.1.10+git20130802-1ubuntu1 on Ubuntu Saucy
  (13.10) and have encountered a memory leak in lrmd.
  
  The details of the bug are covered here in this thread
  (http://oss.clusterlabs.org/pipermail/pacemaker/2014-May/021689.html)
  but to summarise, the Pacemaker developers believe the leak is caused by
  the g_dbus API, the use of which was removed in Pacemaker 1.11.
  
  I've also attached the Valgrind

[Bug 1750741] Re: Memory leak in g_dbus_proxy_new_for_bus_sync()

2018-02-20 Thread Seyeong Kim

** Patch added: "lp1750741_trusty_glib2.0.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1750741/+attachment/5059468/+files/lp1750741_trusty_glib2.0.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1750741

Title:
  Memory leak in g_dbus_proxy_new_for_bus_sync()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1750741/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1750741] [NEW] Memory leak in g_dbus_proxy_new_for_bus_sync()

2018-02-20 Thread Seyeong Kim

Public bug reported:

[Impact]

This issue is found while debugging pacemaker lrmd memory leak

glib2.0 gio function g_dbus_proxy_new_for_bus_sync has leak as [1] said

this is affected to Trusty

[Test Case]

https://pastebin.ubuntu.com/p/fqK6Cx3SKK/
you can check memory leak with this script

[Regression]
This patch is affected to library pkg. so related daemon should be restarted 
after patching. patch itself is very simple and old. it seems verified for few 
years.

[Others]

original commit

https://gitlab.gnome.org/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: Fix Released


** Tags: sts sts-sru-needed

** Tags added: sts sts-sru-needed

** Also affects: glib2.0 (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: pacemaker (Ubuntu)

** Changed in: glib2.0 (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1750741

Title:
  Memory leak in g_dbus_proxy_new_for_bus_sync()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1750741/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1711936] Re: Severe graphical corruption in gnome-shell with nouveau [Nvidia GeForce 8400M GS]

2018-02-20 Thread Launchpad Bug Tracker

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1711936

Title:
  Severe graphical corruption in gnome-shell with nouveau [Nvidia
  GeForce 8400M GS]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1711936/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1711936] Re: Severe graphical corruption in gnome-shell with nouveau [Nvidia GeForce 8400M GS]

2018-02-20 Thread Launchpad Bug Tracker

[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1711936

Title:
  Severe graphical corruption in gnome-shell with nouveau [Nvidia
  GeForce 8400M GS]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1711936/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1735127] Re: Ubuntu AA (gnome) - panel and dock transparency animation crashes Gnome shell

2018-02-20 Thread Launchpad Bug Tracker

[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1735127

Title:
  Ubuntu AA (gnome) - panel and dock transparency animation crashes
  Gnome shell

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1735127/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1732704] Re: Window opened with shortcut custom global shortcut does not get focus

2018-02-20 Thread Launchpad Bug Tracker

[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1732704

Title:
  Window opened with shortcut custom global shortcut does not get focus

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1732704/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1736820] Re: Laptop doesn't suspend on lid close

2018-02-20 Thread Launchpad Bug Tracker

[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1736820

Title:
  Laptop doesn't suspend on lid close

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1736820/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1731872] Re: gnome shell crashed when searching for 're'

2018-02-20 Thread Launchpad Bug Tracker

[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1731872

Title:
  gnome shell crashed when searching for 're'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1731872/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1750352] Re: gnome-shell freeze on key press while high CPU load

2018-02-20 Thread Daniel van Vugt

Thanks. Your system log is full of error messages about 'extensions'
that I have never seen before. Like:

fÃ©vr. 20 11:55:15 hostname nautilus[2460]: Unexpected plugin response. This
probably indicates a bug in a Nautilus extension: handle=0x55d6331da690
fÃ©vr. 20 11:55:15 hostname nautilus[2460]: Unexpected plugin response. This
probably indicates a bug in a Nautilus extension: handle=0x55d6334b7770
fÃ©vr. 20 11:55:15 hostname nautilus[2460]: Unexpected plugin response. This
probably indicates a bug in a Nautilus extension: handle=0x55d63425e160

and

fÃ©vr. 20 12:43:51 hostname gnome-shell[2029]: JS ERROR: ReferenceError:
NM80211ApFlags is not defined
WirelessList<._getApSecurityType@/home/username/.local/share/gnome-shell/extensions/extend-panel-menu@julio641742/indicators/network.js:448:1
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22

WirelessList<._accessPointAdded@/home/username/.local/share/gnome-shell/extensions/extend-panel-menu@julio641742/indicators/network.js:567:27

Please try disabling/uninstalling all gnome-shell extensions other than
the Ubuntu default ones (gnome-shell-extension-appindicator, gnome-
shell-extension-ubuntu-dock), and tell us if the bug persists. If that
fixes it then please try to figure out which extension was causing the
bug, by reintroducing them one-by-one.

--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1750352

91 matches

Mail list logo