Page 2 of 2 FirstFirst 12
Results 11 to 14 of 14

Thread: Reporting bug in 18.04

  1. #11
    Join Date
    Jul 2019
    Beans
    6

    Re: Reporting bug in 18.04

    Thanks for the suggestion. I'm not getting overheating, though; just high CPU usage leading to freeze-up.

    Just tried the same page via Chrome, and it is running three separate chrome processes totaling 120% CPU. True on a few other pages too, always ones running Javascript.

    Don't know enough about how Ubuntu/Firefox/Chrome implement Javascript to know where to go from there...

    As for killing and restarting, when this happens it freezes hard enough that I can't access the system monitor or terminal. Can move the cursor around, but keyboard is nonresponsive and nothing else works. So that's not an option.
    Last edited by barking63; August 4th, 2019 at 07:37 PM.

  2. #12
    Join Date
    Sep 2009
    Location
    Pennsylvania
    Beans
    2,774
    Distro
    Xubuntu

    Re: Reporting bug in 18.04

    The only thought I have right now: if it were my machine, I would try Xubuntu on it. Xubuntu is a much lighter desktop and just might solve your problem. Even if you aren't sure, make a boot medium with Xubuntu 18.04 and run the machine from that and see what happens. If all seems good, install it. You could also make it dual boot with Ubuntu.

  3. #13
    Join Date
    Aug 2012
    Beans
    12

    Re: Reporting bug in 18.04

    How much RAM do you have installed? I think you need at least 4Gb these days with the huge webpage content, scripts etc. If you want to run Fire Fox with multiple tabs. e.g 4tabs could push you over 2Gb this would require the CPU to work over time shuffling stuff on/off the Swap space.
    I recently had to increase from 2Gb to 4Gb because of the slowing down of everything.
    Ubuntu 18.04.2 64bit 250Gb HD 4GB RAM 0 swap space.
    Intel® Core™2 Duo CPU E7500 @ 2.93GHz × 2

  4. #14
    Join Date
    Jun 2007
    Location
    norway
    Beans
    31
    Distro
    Ubuntu Development Release

    Re: Reporting bug in 18.04

    hey.
    i've a almost the same problem while firefox is running. WEB Content runs up all cores to a 100% when i start any application that requires root powers. this happens only on my laptop and only while running root applictons. i run journalctl -xb and top to might locate the issue but as far i can see through the output from journalctl -xb i can't see anything unusual. while the cpu is at full load, journalctl -xb gives no output. the only thing i noticed that WEB content thingy running at full load.
    -- Logs begin at Tue 2018-05-29 19:51:06 CEST, end at Sun 2019-09-01 14:31:04 CEST. --
    sep. 01 14:24:53 ko81x2 kernel: microcode: microcode updated early to revision 0x21, date = 2019-02-13
    sep. 01 14:24:53 ko81x2 kernel: Linux version 4.15.0-60-generic (buildd@lgw01-amd64-030) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 (Ubuntu 4.15.0-60.67-generic 4.15.18)
    sep. 01 14:24:53 ko81x2 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-60-generic root=UUID=7e6b3a00-6150-4808-bfbc-8ff2654c8b48 ro quiet splash vt.handoff=7
    sep. 01 14:24:53 ko81x2 kernel: KERNEL supported cpus:
    sep. 01 14:24:53 ko81x2 kernel: Intel GenuineIntel
    sep. 01 14:24:53 ko81x2 kernel: AMD AuthenticAMD
    sep. 01 14:24:53 ko81x2 kernel: Centaur CentaurHauls
    sep. 01 14:24:53 ko81x2 kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
    sep. 01 14:24:53 ko81x2 kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
    sep. 01 14:24:53 ko81x2 kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
    sep. 01 14:24:53 ko81x2 kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
    sep. 01 14:24:53 ko81x2 kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
    sep. 01 14:24:53 ko81x2 kernel: e820: BIOS-provided physical RAM map:
    sep. 01 14:24:53 ko81x2 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d3ff] usable
    sep. 01 14:24:53 ko81x2 kernel: BIOS-e820: [mem 0x000000000009d400-0x000000000009ffff] reserved
    sep. 01 14:24:53 ko81x2 kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
    sep. 01 14:24:53 ko81x2 kernel: BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
    sep. 01 14:24:53 ko81x2 kernel: BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved
    sep. 01 14:24:53 ko81x2 kernel: BIOS-e820: [mem 0x0000000020200000-0x0000000040003fff] usable
    sep. 01 14:24:53 ko81x2 kernel: BIOS-e820: [mem 0x0000000040004000-0x0000000040004fff] reserved
    sep. 01 14:24:53 ko81x2 kernel: BIOS-e820: [mem 0x0000000040005000-0x000000009ffaffff] usable
    sep. 01 14:24:53 ko81x2 kernel: BIOS-e820: [mem 0x000000009ffb0000-0x00000000a13affff] reserved
    sep. 01 14:24:53 ko81x2 kernel: BIOS-e820: [mem 0x00000000a13b0000-0x00000000aa3befff] usable
    sep. 01 14:24:53 ko81x2 kernel: BIOS-e820: [mem 0x00000000aa3bf000-0x00000000aaebefff] reserved
    sep. 01 14:24:53 ko81x2 kernel: BIOS-e820: [mem 0x00000000aaebf000-0x00000000aafbefff] ACPI NVS
    sep. 01 14:24:53 ko81x2 kernel: BIOS-e820: [mem 0x00000000aafbf000-0x00000000aaffefff] ACPI data
    sep. 01 14:24:53 ko81x2 kernel: BIOS-e820: [mem 0x00000000aafff000-0x00000000aaffffff] usable
    sep. 01 14:24:53 ko81x2 kernel: BIOS-e820: [mem 0x00000000ab000000-0x00000000af9fffff] reserved
    sep. 01 14:24:53 ko81x2 kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
    sep. 01 14:24:53 ko81x2 kernel: BIOS-e820: [mem 0x00000000feb00000-0x00000000feb03fff] reserved
    sep. 01 14:24:53 ko81x2 kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
    sep. 01 14:24:53 ko81x2 kernel: BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
    sep. 01 14:24:53 ko81x2 kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
    sep. 01 14:24:53 ko81x2 kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
    sep. 01 14:24:53 ko81x2 kernel: BIOS-e820: [mem 0x00000000ffb80000-0x00000000ffffffff] reserved
    sep. 01 14:24:53 ko81x2 kernel: BIOS-e820: [mem 0x0000000100000000-0x000000024f5fffff] usable
    sep. 01 14:24:53 ko81x2 kernel: NX (Execute Disable) protection: active
    sep. 01 14:24:53 ko81x2 kernel: SMBIOS 2.7 present.
    sep. 01 14:24:53 ko81x2 kernel: DMI: Dell Inc. Vostro 3560/05GV6H, BIOS A17 04/14/2014
    sep. 01 14:24:53 ko81x2 kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
    sep. 01 14:24:53 ko81x2 kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
    sep. 01 14:24:53 ko81x2 kernel: e820: last_pfn = 0x24f600 max_arch_pfn = 0x400000000
    sep. 01 14:24:53 ko81x2 kernel: MTRR default type: uncachable
    sep. 01 14:24:53 ko81x2 kernel: MTRR fixed ranges enabled:
    sep. 01 14:24:53 ko81x2 kernel: 00000-9FFFF write-back
    sep. 01 14:24:53 ko81x2 kernel: A0000-BFFFF uncachable
    sep. 01 14:24:53 ko81x2 kernel: C0000-E7FFF write-protect
    sep. 01 14:24:53 ko81x2 kernel: E8000-EFFFF write-combining
    sep. 01 14:24:53 ko81x2 kernel: F0000-FFFFF write-protect
    sudo apt-get moo
    Ubuntu on a 50" 1920×1080

Page 2 of 2 FirstFirst 12

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •