[Bug 720446] Re: memory leak in compiz when using places, dashboard, and exposing launcher icons with multiple quicklists
I ran another log, which has a pretty interesting result. I didn't use my computer at all yesterday while the log was running, it was idle all the time. Its memory usage increased over time, from about 26MB when I left it, to about 521M when I came back. That is a huge increase by itself, for a system that is not being used. But the really interesting part comes when I logged in to my computer, at 09:46:35 in the log. Memory usage suddenly jumped from about 521MB to about 1.3GB! And it also had 3715 minflt/s (minor page faults per second? I'm not sure what this is). There is definitely something very, very much broken in Compiz. ** Attachment added: compiz3.log https://bugs.launchpad.net/ubuntu/+source/unity/+bug/720446/+attachment/2255820/+files/compiz3.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/720446 Title: memory leak in compiz when using places, dashboard, and exposing launcher icons with multiple quicklists To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-multiload/+bug/720446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 720446] Re: memory leak in compiz when using places, dashboard, and exposing launcher icons with multiple quicklists
I am also experiencing very high memory usage with compiz, but unlike most reports I'm not using any kind of system monitor, dashboard or whatever thing. I'm using a normal Gnome session with nothing but a few application icons on my panel. Over the past weekend, the memory usage went up to 2.5GB. And since a reboot yesterday it went up to about 600MB right now. Attached is a compiz.log with memory shown increasing over night. I wasn't using the computer. I had Firefox, a terminal and IntelliJ Idea open. The log also contains a list of running processes. It's not a big deal for me, having 8GB of RAM in this machine, but it sure is an annoying bug. I'm not sure if I'm using unity or classic, or whatever. I know I disabled that new stuff of Ubuntu and just selected Gnome as session. ** Attachment added: Compiz memory log and process list https://bugs.launchpad.net/ubuntu/+source/unity/+bug/720446/+attachment/2251155/+files/compiz2.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/720446 Title: memory leak in compiz when using places, dashboard, and exposing launcher icons with multiple quicklists To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-multiload/+bug/720446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 158433] Re: KNetworkManager connect button disabled w/stored key
Dear Kubuntu people, I have tried out Kubuntu 8.4 because I like KDE 3.5 very much, it is very stable. I tried to connect to my wireless network, but I had a problem. After searching on Google I ended up on this page, so I hope my additions will be valuable. I right-clicked the KNetworkManager icon to connect to my Wireless network. I selected my network and it prompted for my key (I think WEP or WPA or so), however the 'Connect' button stayed disabled. I went to another computer and visited the configuration page of my router where my key is displayed. It turned out I had my key all wrong. I was trying to type in a password (stupidly enough, my router password), but whilst typing the button remained disabled. However after a certain amount of characters, the button became enabled. I then occurred to me that probably there is a minimum length of the key, which was not met by the shorter password I tried to enter. It would be far more clear if either of the following happened: - Connect button is enabled, I try to click it and a message appears saying that it is wrong (it knows so by seeing it's not long enough), or - When the key is not long enough it should display a message or something similar indicating that. In either case I would have known that the key I was trying to enter was in fact invalid, because it simply was too short, instead of me getting frustrated and wondering why the button was disabled (I honestly thought there was a defect with the program). I hope this information helps you make a better product in the future (not that I'm implying it's not good now, because it sure is for the most part). Kind regards, Paul -- KNetworkManager connect button disabled w/stored key https://bugs.launchpad.net/bugs/158433 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
