Unity webapps crash Ubuntu 14.04 LTS on my computer

Bug #1309044 reported by Josema
50
This bug affects 9 people
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Expired
Low
Unassigned

Bug Description

SInce I installed Ubuntu 14.04 LTS some weeks ago, every time I started the new Ubuntu web browser and started using it there was a time when Ubuntu stopped working and I could only move the cursor, without being able to switch to a terminal window or anything else. The only thing I could do is to turn off my computer from the power button.

Now I have reinstalled Ubuntu 14.04 LTS again and the problem still appears in Unity webapps like Twitter. Unfortunately, my computer did not give me any crash report or anything to send, but I can only send my laptop information.

I'm using a Sony VPFC12M1E/H laptop with an Intel Core i5, 4 GB of RAM, a NVIDIA GeForce GT 330M (with a nouveau driver) and a dual boot with Windows 8.1 Update 1.

Josema (jmvalbuenap)
affects: ubuntu-clock-app → unity-webapps-twitter
Revision history for this message
David Barth (dbarth) wrote :

Can you confirm that webapps are executed by webapp-container and a set of oxide render processes?

In which case that may be due to GL issues between that runtime and your card/driver combination.

Revision history for this message
David Barth (dbarth) wrote :

BTW, can you also verify the presence of a crash report in /var/crash ? Thanks

Revision history for this message
Josema (jmvalbuenap) wrote :

There is no crash report in /var/crash. How can I confirm that webapps are executed by webapp-container?

Revision history for this message
Josema (jmvalbuenap) wrote :

Well, I have enabled the privative NVIDIA 331.38 driver, and it looks like the webapps do not crash anymore. This means there is a problem related to the NVIDIA GeForce GT 330M and the nouveau driver which is causing Ubuntu 14.04 to crash

Revision history for this message
David Barth (dbarth) wrote :

Thanks a lot for reporting this test result.

no longer affects: unity-webapps-twitter
no longer affects: webbrowser-app
Revision history for this message
ausnahmefehler (ausnahmefehler) wrote :

I installed Ubuntu 14.04 64bit; I have the same problem; it only appears when using firefox and at the same time web-apps (e.g. AMAZON)... then the system crashes completly.. only thing I can do is powerbutton or ssh-login and reboot....
When I use the web-app without having firefox started, I think there are no problems..

Revision history for this message
Alexandre Abreu (abreu-alexandre) wrote :

Switching away from nouveau drivers for the nvidia ones, seems to make the issue go away in all the instances of this bug.

Add oxide as the common ground for all those issues, it is the web engine backend the webapp container.

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Maarten, any ideas about how to figure out what's going on with this?

Revision history for this message
saurabh shabdik (kobirshamim) wrote :

Yes. web browser and telegram also showing the same behavior.

Revision history for this message
Bob Ball (bob-ball) wrote :
Revision history for this message
Jeff (1rockingpenguinau) wrote :

Same issues here on Fm2 Board,after recent firmware updates.
Hard Locks and various random lockups ,more prevalent on xen hypervisor host,but occurs in both.
Also firefox crashing with nouveau errors related to page mapping.

Occurs during https access and encrypted pages.

Attached log.

Very unreliable since the recent update ,looks similair to the 2012 bug with nouveau or other firmware.
Regressing ..........

Chromium doesnt seem affected.

Tried nvidia prop drivers which stopped machine from booting .

Revision history for this message
Jeff (1rockingpenguinau) wrote :

Will try upstream and regression .

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xserver-xorg-video-nouveau (Ubuntu):
status: New → Confirmed
Revision history for this message
Maarten Lankhorst (mlankhorst) wrote :

The second bug was definitely a dupe, the problem seems to be with threaded opengl. Nouveau does not currently support this..

The following hack fixes the issue in a nasty way by creating separate screen objects with the same drm device. libdrm is only thread-safe with libdrm 2.4.54 or later. This probably won't break vdpau, though I'm not completely sure..

The real fix is making nouveau thread-safe, it's been discussed on the #nouveau channel:

http://people.freedesktop.org/~cbrill/dri-log/?channel=nouveau&date=2014-06-04

Changed in xserver-xorg-video-nouveau (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Is this still a problem with Oxide 1.4.2? We're populating the GPU info now, which means that GPU feature blacklisting should work correctly and all GPU features are currently blacklisted in Chromium for the nouveau drivers.

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Basically, we should fall back to software compositing now and disable things like WebGL, meaning that the only thread that accesses opengl is the Qt render thread.

penalvch (penalvch)
no longer affects: xserver-xorg-video-nouveau (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xorg (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Josema, thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect -p xorg 1309044

Please ensure you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

affects: nouveau → xorg (Ubuntu)
no longer affects: xorg (Ubuntu)
Changed in xorg (Ubuntu):
status: New → Confirmed
penalvch (penalvch)
affects: oxide → xorg (Ubuntu)
Changed in xorg (Ubuntu):
status: New → Incomplete
importance: Undecided → Low
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for xorg (Ubuntu) because there has been no activity for 60 days.]

Changed in xorg (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.