Bug 1139777 - 3.12.6 crashes after a few seconds
Summary: 3.12.6 crashes after a few seconds
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: webkitgtk3
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-09 15:29 UTC by Matthias Clasen
Modified: 2015-12-02 16:16 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-12-02 03:46:03 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
full stacktrace (54.30 KB, text/plain)
2014-09-09 15:29 UTC, Matthias Clasen
no flags Details
mbox (52.75 KB, text/plain)
2014-09-12 14:49 UTC, Matthias Clasen
no flags Details

Description Matthias Clasen 2014-09-09 15:29:57 UTC
Created attachment 935796 [details]
full stacktrace

evolution 3.12.6 crashes after a few seconds here:

evolution: cairo-scaled-font.c:459: _cairo_scaled_glyph_page_destroy: Assertion `!scaled_font->cache_frozen' failed.

This is with webkitgtk3-2.4.5-3.fc21

Comment 1 Matthias Clasen 2014-09-09 19:51:19 UTC
after starting evolution with --disable-preview and deleting a few messages in my inbox, this is no longer happening. So I assume this must have been due to the content of one specific message that is now gone :-(

Comment 2 Milan Crha 2014-09-10 06:47:04 UTC
In case you didn't expunge yet, then the message can be seen either in the Trash folder (of the account you deleted the message at) or use View->Show deleted message, where those stroke-through are deleted.

Comment 3 Matthias Clasen 2014-09-12 14:48:36 UTC
happened again today. I'll attach the offending message

Comment 4 Matthias Clasen 2014-09-12 14:49:03 UTC
Created attachment 936991 [details]
mbox

Comment 5 David Woodhouse 2014-09-12 15:08:56 UTC
FWIW I can happily view this email in Evolution 3.12 under F20 (with webkitgtk3-2.2.7-3.fc20)

Comment 6 Tomas Popela 2014-09-15 06:53:46 UTC
I can view it on Evolution 3.13.6 (current master) and the latest webkitgtk3 - 2.4.5. So I really don't know if it is the webkitgtk fault or just something regarding to F21 as I'm testing on F20..

Comment 7 Milan Crha 2014-09-15 10:48:10 UTC
I tried with current rawhide:
  webkitgtk3-2.4.5-4.fc22.x86_64
  cairo-1.13.1-0.4.git337ab1f.fc22.x86_64
  evolution-3.13.5-1.fc22.x86_64
  gtk3-3.13.8-1.fc22.x86_64
  glib2-2.41.4-3.fc22.x86_64
and it also survives without any issues.

Comment 8 Fedora End Of Life 2015-11-04 10:43:51 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 9 Fedora End Of Life 2015-12-02 03:46:06 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.