[Dx-packages] [Bug 1589605] Re: evolution-calendar-factory uses lots of memory
[Expired for evolution-data-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: evolution-data-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1589605 Title: evolution-calendar-factory uses lots of memory Status in evolution package in Ubuntu: Invalid Status in evolution-data-server package in Ubuntu: Expired Status in indicator-datetime package in Ubuntu: Expired Bug description: As filed under bug #1342123 (under Canonical System Image, i.e. for mobile installs) by several users, including desktop installs, evolution-calendar-factory (previsouly in 14.04) then evolution-calendar-factory-subprocess (in 16.04) run using several hundreds of megabytes of memory (~ 300 Mio in my case). This might have to do with having lots of linked calendars (Google Agenda or other). Another user on my system has much fewer Google Agendas than me and her memory usage of evolution-calendar-factory-subprocess is less, but still close to 100 Mio. There have been random crashes of the process, mostly directly upon login, always caused by addressing memory out of range. There used to be a workaround by invoking the process a second time, which caused it to exit more or less gracefully. This is not the case anymore in 16.04. Unfortunately, searching Google leads to the bug #1342123 which concerns "Canonical System Image", and several users have replied even though it does not only concern mobile installs, which is not immediately self-evident when you are not aware what "Canonical System Image" stands for… To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1589605/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1589605] Re: evolution-calendar-factory uses lots of memory
[Expired for indicator-datetime (Ubuntu) because there has been no activity for 60 days.] ** Changed in: indicator-datetime (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1589605 Title: evolution-calendar-factory uses lots of memory Status in evolution package in Ubuntu: Invalid Status in evolution-data-server package in Ubuntu: Expired Status in indicator-datetime package in Ubuntu: Expired Bug description: As filed under bug #1342123 (under Canonical System Image, i.e. for mobile installs) by several users, including desktop installs, evolution-calendar-factory (previsouly in 14.04) then evolution-calendar-factory-subprocess (in 16.04) run using several hundreds of megabytes of memory (~ 300 Mio in my case). This might have to do with having lots of linked calendars (Google Agenda or other). Another user on my system has much fewer Google Agendas than me and her memory usage of evolution-calendar-factory-subprocess is less, but still close to 100 Mio. There have been random crashes of the process, mostly directly upon login, always caused by addressing memory out of range. There used to be a workaround by invoking the process a second time, which caused it to exit more or less gracefully. This is not the case anymore in 16.04. Unfortunately, searching Google leads to the bug #1342123 which concerns "Canonical System Image", and several users have replied even though it does not only concern mobile installs, which is not immediately self-evident when you are not aware what "Canonical System Image" stands for… To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1589605/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1610527] Re: 00:00 for all-day events in the Calendar indicator
** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Importance: Undecided => Medium ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Milestone: None => backlog ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Alejandro J. Cura (alecu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1610527 Title: 00:00 for all-day events in the Calendar indicator Status in Canonical System Image: Confirmed Status in Ubuntu UX: New Status in indicator-datetime package in Ubuntu: New Bug description: bq M10 rc-proposed For all-day events like birthdays, showing 00:00 in the calendar indicator is IMO a waste of space. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1610527/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1609793] Re: Unity tests crashes when compiling google-mocks with gcc-6
** Changed in: google-mock (Debian) Status: Unknown => Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to google-mock in Ubuntu. https://bugs.launchpad.net/bugs/1609793 Title: Unity tests crashes when compiling google-mocks with gcc-6 Status in google-mock package in Ubuntu: Fix Released Status in google-mock package in Debian: Fix Committed Bug description: Ubuntu Unity tests fails when using gcc-6, because test-gtest causes a crash. Starting program: /tmp/unity-7.5.0+16.10.20160804/obj-x86_64-linux-gnu/tests/test-gtest [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe0f1d700 (LWP 22778)] [New Thread 0x7fffdbfff700 (LWP 22779)] [New Thread 0x7fffdb7fe700 (LWP 22780)] [==] Running 1637 tests from 105 test cases. [--] Global test environment set-up. [--] 14 tests from TestActionLink [ RUN ] TestActionLink.AligmentCorrectlySetDifferent Thread 1 "test-gtest" received signal SIGSEGV, Segmentation fault. testing::internal::FunctionMockerBase::InvokeWith(std::tuple<> const&) (args=empty std::tuple, this=0x7fffdb08) at /usr/include/gmock/gmock-spec-builders.h:1530 1530 this->UntypedInvokeWith())->GetValueAndDelete(); #0 testing::internal::FunctionMockerBase::InvokeWith(std::tuple<> const&) (args=empty std::tuple, this=0x7fffdb08) at /usr/include/gmock/gmock-spec-builders.h:1530 No locals. #1 testing::internal::FunctionMocker::Invoke() (this=0x7fffdb08) at /usr/include/gmock/gmock-generated-function-mockers.h:76 No locals. #2 unity::dash::ActionLinkMock::QueueDraw (this=0x7fffd3c0) at /tmp/unity-7.5.0+16.10.20160804/tests/test_action_link.cpp:43 No locals. #3 0x559ce574 in unity::dash::ActionLink::set_underline (this=0x7fffd3c0, underline=unity::StaticCairoText::NUX_UNDERLINE_NONE) at /tmp/unity-7.5.0+16.10.20160804/tests/../dash/previews/ActionLink.cpp:218 No locals. #4 0x559d53bf in std::function::operator()(unity::StaticCairoText::UnderlineState const&) const (__args#0=, this=0x7fffda00) at /usr/include/c++/6/functional:2136 No locals. #5 nux::RWProperty::Set (this=0x7fffd9c8, value=) at /usr/include/Nux-4.0/NuxCore/Property-inl.h:218 No locals. #6 0x559d0c31 in unity::dash::TestActionLink_UnderlineCorrectlySetDifferent_Test::TestBody (this=) at /tmp/unity-7.5.0+16.10.20160804/tests/test_action_link.cpp:116 A fix is available at https://github.com/google/googletest/issues/705#issuecomment-235067917 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-mock/+bug/1609793/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1199877] Re: unity-panel-service memory leak and 100% CPU usage
I'm using the owncloud client - thanks "nazar-pc", for your hint. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-appmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1199877 Title: unity-panel-service memory leak and 100% CPU usage Status in Application Menu Indicator: Fix Released Status in Application Menu Indicator 13.10 series: Fix Released Status in The Ubuntu Power Consumption Project: Fix Released Status in Unity: Invalid Status in Ubuntu: Fix Released Status in indicator-appmenu package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Status in The Saucy Salamander: Fix Released Status in indicator-appmenu source package in Saucy: Fix Released Bug description: Impact: high CPU/memory usage from unity-panel-service Test case: Open a large image in the GIMP and activate a lot of items from the global menu. Using shortcuts is enough and faster to reproduce this bug (I've always used Ctrl+A and Ctrl+Shift+A). Memory usage of unity- panel-service increases steadily and it uses a lot of CPU shortly after activating the menu items in a short time. Regression potential: check that the menus are stable/working as they should - Just going about my business on Ubuntu Raring amd64 on an x230 and I heard the fan kick into action. top showed me that unity-panel-service was consuming all the free cycles on one of my CPUs. I killed it before my machine overheated, so I didn't attach a debugger to see why it was totally pegging out a CPU. I'm not sure if this adds any context, but I was using a LibreOffice spreadsheet and I could not insert a table because the menu had lost it's mind, and then I observed the overly loaded CPU a very short while after that. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/1199877/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
