date:20171011

[Desktop-packages] [Bug 1722811] Re: gnome-shell crashed with SIGSEGV in meta_workspace_get_work_area_for_monitor()

2017-10-11 Thread Treviño

** Bug watch added: GNOME Bug Tracker #788860
   https://bugzilla.gnome.org/show_bug.cgi?id=788860

** Also affects: gnome-shell via
   https://bugzilla.gnome.org/show_bug.cgi?id=788860
   Importance: Unknown
   Status: Unknown

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

Title:
  gnome-shell crashed with SIGSEGV in
  meta_workspace_get_work_area_for_monitor()

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  When I set the Scale of the Built-in display at gnome-control-center >
  Devices > Displays from 200% to 100% and click "Apply", the gnome-
  shell session crashed and brought me back to the login screen.

  As per duplicates, this also happens on startup or suspend/resume.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 09:37:07 2017
  DisplayManager: lightdm
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 
'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 
'ubuntu-amazon-default.desktop', 'gnome-control-center.desktop', 
'hexchat.desktop', 'chromium-browser.desktop', 'chromium_chromium.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-03-14 (211 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170228)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fc7a0cfa877 
:  movdqu 0x8(%rax),%xmm0
   PC (0x7fc7a0cfa877) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%xmm0" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_workspace_get_work_area_for_monitor () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /usr/lib/libgjs.so.0
   ?? () from /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in 
meta_workspace_get_work_area_for_monitor()
  UpgradeStatus: Upgraded to artful on 2017-10-11 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1722998] [NEW] VMware memory allocation process ... HUGE RESOURCE HIT ?

2017-10-11 Thread AIAMUZZ

Public bug reported:

Hi,

I am writing this with concerns on the way RAM(memory) is handled by the
same software(VMware Workstation) across different versions of the
Ubuntu OS.

I am however unsure if the concern i am reporting here is actually a Bug
... or ... a feature that has been withdrawn on purpose ... or ... a
feature that's got overlooked from kernel to kernel updates.

How did i stumble upon this issue ?

My primary daily driver OS is Ubuntu 14.04 (ker. 3.13), i use VMware
workstation on this host to run Windows 7 to run my work software which
does not have a linux version. While my VM guest*Windows 7) has been
allocated 8GB of RAM the RAM usage on my Host shows no more than 3-4GB.

I while back i had installed Ubuntu 16.04 on an adjacent partition and
tried running a copy of the exact same VM guest and to my shock saw that
right from boot the entire 8GB of RAM gets blocked on the host system.

What was earlier 3-4 GB of RAM consumption in Ubuntu 14.04 now shot up
to a whopping 10-11GB in Ubuntu 16.04. A HUGE resource hit.

Now i am test driving Deepin OS i find the same resource hit on this OS
too just like the one experienced on Ubuntu 16.04 ... 10-12 GB of RAM is
affected the moment i boot up my vm machine. I am using an exact same
copy from Ubuntu 14.04 to run even here.

What additional test's have i done to probe this issue ?

I have tested this HUGE RESOURCE HIT on the following versions ... I
used the exact same version of VMware Workstation on my test OS's as
well as the latest version of VMware workstation, following are the
findings.

software version tested on ...

VMware Workstation 12.1.0
VMware Workstation 14

OS versions tested on ...

Ubuntu 14.04 (Ker. 3.13)
Ubuntu 15.04 (Ker. 3.19)
Ubuntu 15.10 (Ker. 4.2)

tests on the above OS's show that the memory is efficiently handled and the
overall memory consumption(both Host and Guest VM included)is roughly around 4
GB even though the VM is configured with 8GB of RAM

UbuntuGnome 16.04 (Ker. 4.4)
Deepin 15.4.1 (Ker. 4.9)
UbuntuGnome 17.04 (Ker. 4.10)

However my tests on these OS resulted in a HUGE RESOURCE HIT ... the
overall memory consumption(both Host and Guest VM included) here has
been a WHOPPING 10-12GB.

What proof do you have of this inconsistency ?

I am attaching a screenshot with the memory consumed marked side by
side.

I have Deepin OS 15.4.1(Ker. 4.9) and Ubuntu 14.04(Ker. 3.13) on my system ...
one demonstrating the resource hog i am reporting ... and ... the other
demonstrating the efficient use of system resources.

So if you require any logs or commands to be run out of both this
environments to further probe this resource leakage please let me know
the direct commands and i'll provide the respective outputs to help you
identify the issue.

PS : I am not a geek but rather consider myself as a power user, hence
direct commands to collect additional info out of the 2 environments
would help.

thanks for looking.

** Affects: xserver-xorg-video-vmware (Ubuntu)
Importance: Undecided
Status: New

** Attachment added: "Memory Resource Hit.png"

https://bugs.launchpad.net/bugs/1722998/+attachment/4968265/+files/Memory%20Resource%20Hit.png

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-vmware in Ubuntu.
https://bugs.launchpad.net/bugs/1722998

Title:
VMware memory allocation process ... HUGE RESOURCE HIT ?

Status in xserver-xorg-video-vmware package in Ubuntu:
New

Bug description:
Hi,

I am writing this with concerns on the way RAM(memory) is handled by
the same software(VMware Workstation) across different versions of the
Ubuntu OS.

I am however unsure if the concern i am reporting here is actually a
Bug ... or ... a feature that has been withdrawn on purpose ... or ...
a feature that's got overlooked from kernel to kernel updates.

How did i stumble upon this issue ?

My primary daily driver OS is Ubuntu 14.04 (ker. 3.13), i use VMware
workstation on this host to run Windows 7 to run my work software
which does not have a linux version. While my VM guest*Windows 7) has
been allocated 8GB of RAM the RAM usage on my Host shows no more than
3-4GB.

I while back i had installed Ubuntu 16.04 on an adjacent partition and
tried running a copy of the exact same VM guest and to my shock saw
that right from boot the entire 8GB of RAM gets blocked on the host
system.

What was earlier 3-4 GB of RAM consumption in Ubuntu 14.04 now shot up
to a whopping 10-11GB in Ubuntu 16.04. A HUGE resource hit.

Now i am test driving Deepin OS i find the same resource hit on this
OS too just like the one experienced on Ubuntu 16.04 ... 10-12 GB of
RAM is affected the moment i boot up my vm machine. I am using an
exact same copy from Ubuntu 14.04 to run even here.

1 2 3 >

1 - 100 of 201 matches

Mail list logo