This bug was fixed in the package webbrowser-app - 0.23+15.04.20141202
~rtm-0ubuntu1
---
webbrowser-app (0.23+15.04.20141202~rtm-0ubuntu1) 14.09; urgency=low
[ Ubuntu daily release ]
* New rebuild forced
[ Olivier Tilloy ]
* Replace the custom favicon image provider with a
** Changed in: webbrowser-app
Status: In Progress = Fix Released
** Changed in: canonical-devices-system-image
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This was a late waiver on rtm so ok to land now
** Changed in: canonical-devices-system-image
Importance: Undecided = High
** Changed in: canonical-devices-system-image
Status: New = Confirmed
** Changed in: canonical-devices-system-image
Milestone: None = ww51-2014
--
You
** Changed in: webbrowser-app
Status: Fix Released = In Progress
** Changed in: webbrowser-app (Ubuntu RTM)
Importance: Undecided = High
** Changed in: webbrowser-app
Importance: Critical = High
** Tags added: ww51
--
You received this bug notification because you are a member of
This bug was fixed in the package webbrowser-app -
0.23+15.04.20141202-0ubuntu1
---
webbrowser-app (0.23+15.04.20141202-0ubuntu1) vivid; urgency=low
[ Ubuntu daily release ]
* New rebuild forced
[ Olivier Tilloy ]
* Replace the custom favicon image provider with a
** Changed in: webbrowser-app
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1395748
Title:
Crash going back twice while loading a page
To manage
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1395748
Title:
Crash going back twice while loading a page
I’ve spent some more time investigating the issue, and it looks to me
like it could be a bug in Qt itself. I’ve filed https://bugreports.qt-
project.org/browse/QTBUG-42875 upstream. While I’m waiting for
confirmation, I’m going to disable the custom favicon image provider to
get rid of the
** Branch linked: lp:~osomon/webbrowser-app/disable-favicon-provider
** Branch linked: lp:~osomon/webbrowser-app/disable-favicon-provider-rtm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1395748
** Changed in: webbrowser-app (Ubuntu)
Status: Confirmed = In Progress
** Changed in: webbrowser-app (Ubuntu RTM)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The side effect of this work around is that favicons will no longer be
cached to disk, which will result in them having to be refetched when
the browser is closed and restarted. The biggest hit would be the
history page, which when opened will fetch all the favicons that are
visible in the view.
I can reproduce it when you quickly tap twice / multiple times
It survives when you tap multiple times, but less rapidly (still 1s).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1395748
Title:
I confirmed this is broken in krillin rtm 169, and added it to to the QA
regression test plan.
I had to go back and forth several times to trigger the crash, but it
still happened within a minute or so.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I’m working on a proper fix, thanks to Florian’s help in nailing the
issue. I will make sure the fix comes with a unit test, so that the
above entry can eventually be removed from the test plan.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I can reproduce (although not 100% of the times) on desktop too. Here is
how the backtrace looks like when ran in gdb:
#0 QCoreApplication::postEvent (receiver=0x3b78820, event=0x7fff40041990,
priority=0)
at kernel/qcoreapplication.cpp:1284
#1 0x7649945e in
I tested a fix similar to
https://code.launchpad.net/~jpakkane/unity8/threadfix/+merge/206948, but
that didn’t help, the crash is still happening. I need to dig further in
QtQuick’s internals to understand how requests to custom image providers
are issued and cancelled.
--
You received this bug
16 matches
Mail list logo