Chromium crashes

[Snowhog]

Yes, I know that many/most here don't use Chromium, preferring Firefox. But, I choose to use Chromium as my primary browser. Since updating yesterday to 14.04, KDE 4.12.2, Chromium will just decide to crash for no apparent reason. It just closes. Anyone else experiences this?

Purged pepflashplugin-installer and reinstalled flashplugin-installer. Made no difference. Chromium still just 'quits'. Reinstalled chromium-browser and flashplugin-installer. No difference. Purged chromium-browser and installed it again. No difference.

Guess I'll just use Firefox for now. Likely an update will resolve what ever the issue is.

[hteles]

Hi.

Here it's working correctly but it's not a new install and this profile it's older than 14.04.

regards.

[richb]

In my experience it is usually a misbehaving extension that causes this behavior.

[dequire]

...Or an older graphics card. I have just gone through this recently. Can I ask what graphics card your using?

[Snowhog]

The GPU is an Intel Integrated Graphics. Have had no such problems with Chromium prior to the upgrade to 14.04.

[dequire]

The GPU is an Intel Integrated Graphics. Have had no such problems with Chromium prior to the upgrade to 14.04.

Ok. Might want to report it to Kubuntu bugs then

[bweinel]

Snowhog,

I loaded up Chromium here on my 14.04 test system. The system uses an Intel 82915G/GV/910GL integrated graphics controller on the motherboard. I browsed a few sites with it over about 30 minutes and didn't have any hanging issues. I did note that a big software update came in earlier this morning... kde went to 4.12.3, so it may have been the earlier revision of the system that was causing issues. I'm running the xorg-video-intel and xorg-video-nouveau drivers here.

cheers,
bill

[Snowhog]

I'm running xserver-xorg-video-intel. KDE is at 4.12.3. The only plugin I have is Adblock Plus.

For a test, I just removed Adblock Plus from Chromium. So far, Chromium isn't 'quiting' as it was before. I'll continue using it and see if it behaves properly.

Nope. It just quit again, even with Adblock Plus removed. Something else is the problem. Interestingly, Chromium running on 32-bit 14.04 laptop doesn't exhibit this issue; just on my 64-bit 14.04.

Back to Firefox.

Added:
I purged Chromium and removed ~/.config/chromium then installed chromium-browser and chromium-browser-l10n anew. No difference at all. Chromium still just quits after a short while. So, it isn't the browser and has to be something about 14.04 itself. Again, hopefully, a subsequent update will fix this.

[schnelle]

I am using Google Chrome (not Chromium) without any problems.

Instead of AdBlock plus I use built in Chrome "click to play" feature. It makes Chrome much faster and lightweight. You can turn on this feature in Settings>Advanced settings>Content settings. You can enable all plugins for specific site (youtube for example) by clicking on the icon in address bar: http://www.ghacks.net/wp-content/upl...-this-page.png

[GreyGeek]

I am running 14.04 with the very latest update from this morning, with KDe 4.12.3. I installed Chromium from the repository awhile ago and ran it for awhile. It runs without problems and closes just fine. Never had an abend. Oh, my laptop has an Intel HD4000 GPU and it uses the same video driver as yours, the i915.

[FONT=courier new][B]lsmod | grep video[/B][/FONT]
uvcvideo               80885  0 
videobuf2_vmalloc      13216  1 uvcvideo
videobuf2_memops       13362  1 videobuf2_vmalloc
videobuf2_core         40664  1 uvcvideo
videodev              134688  2 uvcvideo,videobuf2_core
video                  19421  3 i915,acer_wmi,nouveau

[Snowhog]

Here, on my HP laptop:

[B]lsmod | grep video[/B]
uvcvideo               80885  0 
videobuf2_vmalloc      13216  1 uvcvideo
videobuf2_memops       13362  1 videobuf2_vmalloc
videobuf2_core         40664  1 uvcvideo
videodev              134688  2 uvcvideo,videobuf2_core
video                  19421  1 i915

[GreyGeek]

mmm... the only difference between your mod list and mine is the presence of the nouveau driver, which mine loads because I have a secondary video chip, the NVidia GT650M, which requires Bumblebee and "optimus", but which I never use because in my experience my HD4000 is just as fast.

[richb]

mmm... the only difference between your mod list and mine is the presence of the nouveau driver, which mine loads because I have a secondary video chip, the NVidia GT650M, which requires Bumblebee and "optimus", but which I never use because in my experience my HD4000 is just as fast.

My mod list is similar to Snowhogs. I blacklisted nouveau quite some time ago when I stopped using Bumblebee.

Acer V5.

richard[~]$  inxi -GGraphics:  Card: Intel 3rd Gen Core processor Graphics Controller 
           X.Org: 1.14.5 drivers: intel (unloaded: fbdev,vesa) Resolution: 1366x768@60.0hz 
           GLX Renderer: Mesa DRI Intel Ivybridge Mobile GLX Version: 3.0 Mesa 9.2.1

[Snowhog]

There is something within a controlling file used by 64-bit chromium-browser that is causing the unwanted termination, and it happens reliably when chromium-browser is launched graphically, i.e., from the K Menu, where the command is: chromium-browser %U

When executed from the CLI with: chromium-browser (without %U)

The browser does not exhibit the unwanted termination. However, the following error (?) is given in the console:

sh: 1: /usr/lib/nspluginwrapper/i386/linux/npviewer: not found

This unwanted termination does not occur on my 32-bit Trusty Tahr laptop (also using KDE 4.12.3) when launched from the K Menu, nor does it show the error (?) when executed from the CLI.

I can probably fix this if I can identify the file containing the reference/pointer to /usr/lib/nspluginwrapper/i386/linux/npviewer. Any ideas of where to look?

Interestingly, npviewer does not exist on either laptop, so I'm a bit piqued as to why the error I'm getting on the 64-bit laptop doesn't appear on the 32-bit.

Added:
Well, having run Chromium launched from the CLI without %U, after about ten minutes, it terminated. This time there is useful information in the console:

paul@tanagra:~$ chromium-browser
*** Error in `chromium-browser': double free or corruption (!prev): 0x00007ff7d4560b00 ***
*** Error in `chromium-browser': malloc(): memory corruption: 0x00007ff7d4326e80 ***
Segmentation fault (core dumped)
paul@tanagra:~$

So it would seem that on my 64-bit 14.04 laptop, Chromium is/maybe exhibiting a memory leak.

Added:
Ubuntu appears to report that Chromium isn't packaged yet for 14.04 (makes sense; 14.04 is still in development). Another 'difference' between my two laptops is that on the 64-bit, the packagte chromium-codecs-ffmpeg-extra is installed and on the 32-bit, chromium-codecs-ffmpeg. chromium-codecs-ffmpeg only includes the free ogg, vorbis and theora codecs. In addition to the patent-free ogg, vorbis and theora codecs, aac/ac3/mpeg4audio/h264/mov/mp3 are also included in chromium-codecs-ffmpeg-extra.

I'm installing chromium-codecs-ffmpeg which removes chromium-codecs-ffmpeg-extra to see if any difference is made.

[GreyGeek]

Wednesday the mesa packages were updated to 10.1.0-rc1. I immediately began experiencing "render right hanging".
I get these messages in the logs:

.... kernel    [56231.013623] [drm] GPU crash dump saved to /sys/class/drm/card1/error
...  kernel    [56231.016521] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0xf909000 ctx 0) at 0xf90ca04

A day later, last Thursday, they were updated again to 10.1.0-rc3. It did not help.

Prior to those updates I had NO video problems at all. My i915 driver was giving me 60fps, sync'd. Since then FireFox gives me occasional, momentary black triangles and rectangles in text boxes and html frames. Also, more indicative of what's happening,
Sometimes Stellarium will show a similar glitch.
It seems to me to be a combination of pressing the left mouse button while inadvertently moving the mouse that causes FireFox to freeze for 10 to 20 seconds before it begins running again.

One recommended fix is to add "i915.semaphores=0" to the kernel line in /etc/default/grub and run grub-update.

I did that and it helped reduce the frequency but didn't eliminate the problem. Interestingly, I installed Chromium from the repository and while running it I have never had a freeze. However, I cannot add or edit a message on this or other forums. When I left click into the text box a new page momentarily flashes and then disappears. But, Chromium is fast and plays youtube videos very nicely.

I am expecting future updates of the mesa package to clear things up. If they don't then I will downgrade to a version before 10.1.0-rc1.