WebApps Unity plugin for Chromium keeps crashing

Here is an example of what happens when it crashes on Facebook.com
(Note that I had clicked "Never ask for this site" many times before.)

Steps to reproduce:

- open an empty chromium,
- open a tab and navigate to a URL for which a WebApp is available but NOT installed (e.g. facebookmessenger),
- wait until you see an infobar inviting one to install the WebApp,
- reload the page until one sees the crash, it usually occurs during the next 2 refreshes,

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

[Regression Risks]

None, the fix is small and mitigated. The worse that can happen is a memory leak (not the case though).

This bug was fixed in the package unity-chromium-extension - 2.4.4-0ubuntu1

---------------
unity-chromium-extension (2.4.4-0ubuntu1) raring; urgency=low

  * New upstream release.
    - No installation process triggered when a url matches more than one URL
      in the list of available apps (LP: #1078325)
    - Bypasses Same Origin Policy checks via toDataURL (LP: #1069817)
    - Extension options page is broken & does not work (LP: #1076452)
    - Race condition related to integration/install infobar (LP: #1068308)
    - WebApps Unity plugin for Chromium keeps crashing (LP: #1070433)
 -- Ken VanDine <email address hidden> Thu, 15 Nov 2012 11:21:16 -0500

Hello Steven, or anyone else affected,

Accepted unity-chromium-extension into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/unity-chromium-extension/2.4.4-0ubuntu0.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

The fix for this bug has been awaiting testing feedback in the -proposed repository for quantal for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository.

This doesn't appear to be crashing for me any more using -proposed

This bug was fixed in the package unity-chromium-extension - 2.4.4-0ubuntu0.2

---------------
unity-chromium-extension (2.4.4-0ubuntu0.2) quantal-security; urgency=low

  * New upstream release.
    - No installation process triggered when a url matches more than one URL
      in the list of available apps (LP: #1078325)
    - Bypasses Same Origin Policy checks via toDataURL (LP: #1069817)
    - Extension options page is broken & does not work (LP: #1076452)
    - Race condition related to integration/install infobar (LP: #1068308)
    - WebApps Unity plugin for Chromium keeps crashing (LP: #1070433)
 -- Ken VanDine <email address hidden> Thu, 15 Nov 2012 15:23:34 -0500

unity-webapp still crash in chromium-browser.

Package: unity-chromium-extension
Status: install ok installed
Priority: optional
Section: gnome
Installed-Size: 201
Maintainer: Ubuntu Desktop Team <email address hidden>
Architecture: amd64
Version: 2.4.8+13.10.20130920.1-0ubuntu1
Replaces: libunity-webapps-chromium
Depends: chromium-browser (>= 20.0.1132.47~r144678-0ubuntu4), unity-webapps-service

Package: chromium-browser
Status: install ok installed
Priority: optional
Section: web
Installed-Size: 136138
Maintainer: Ubuntu Developers <email address hidden>
Architecture: amd64
Version: 30.0.1599.114-0ubuntu1~cm0saucy

Le 26/10/2013 09:44, shantanu saha a écrit :
> unity-webapp still crash in chromium-browser.
Do you have a stack trace or a way to reproduce the issue?