This is a huge diff, not just "a few minor changes" IMO. Its sort of shocking that glib adds so much in a a few "patch" releases. I know some of these things are for non-Linux platforms, but its really quite hard to separate them out.
If this is just a one line fix, why aren't we just cherry picking the one line fix for this bug? Thats typically how we control regression potential. I'm digging through the diff (34,000 lines!) but at this point I can't really justify the time to review it all. Can somebody update the test case to include a comprehensive test plan so we can get enough test coverage, or re-upload with just the fix for this bug? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/998521 Title: whoopsie process is leaking memory Status in Whoopsie Daisy: Fix Released Status in “glib2.0” package in Ubuntu: Fix Committed Status in “whoopsie-daisy” package in Ubuntu: Confirmed Status in “glib2.0” source package in Precise: Fix Committed Status in “whoopsie-daisy” source package in Precise: Confirmed Status in “glib2.0” source package in Quantal: Fix Committed Status in “whoopsie-daisy” source package in Quantal: Confirmed Bug description: Impact: stable update from the upstream serie including a fix for a leak affecting the default Ubuntu bug reporting tool (whoopsie) Development Fix: the fix is in upstream glib git and will be in q with the next update Stable Fix: the fix is a one liner, the new version has some extra changes Test Case: watch the whoopsie memory usage over time, it should be stable Regression Potential: it's glib, the update should be carefully tested I have a 12.04 server running for 7 days and today I noticed some things started to be swapped out. top shows: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1975 whoopsie 20 0 2649m 1.4g 484 S 0 18.5 14:05.67 whoopsie with 1.4g residential memory. There were 2 crashed applications, facter with .crash file is 2.8Mb and landscape-sysinfo of 17K so it does not look like it is related. I will keep the process running in case i can provide more information and will monitor the process to see whether it is leaking memory. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: whoopsie 0.1.32 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 CrashReports: 640:0:111:17379:2012-05-05 10:59:39.677061820 +0300:2012-05-05 10:59:39.673061820 +0300:/var/crash/_usr_bin_landscape-sysinfo.0.crash 640:0:111:2838166:2012-05-07 00:54:24.435092602 +0300:2012-05-07 00:54:19.759092709 +0300:/var/crash/_usr_bin_facter.0.crash Date: Sat May 12 21:41:18 2012 InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 (20120424.1) SourcePackage: whoopsie-daisy UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/whoopsie-daisy/+bug/998521/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
