GNOME Bugzilla – Bug 656796
Epiphany crashes when I go to https://mail.google.com/mail
Last modified: 2012-10-05 04:27:21 UTC
What should be happening :- a. Open epiphany-browser b. Go to your mail account (already signed in) to https://mail.google.com/mail c. Read your mails. What happens instead :- a. Open epiphany-browser b. If I go to https://mail.google.com/mail c. Epiphany crashes. Attach the backtrace in a minute.
Created attachment 194096 [details] just the backtrace, threads not applied (small backtrace)
Pasting the partial trace outside Program received signal SIGSEGV, Segmentation fault. WebCore::AXObjectCache::getOrCreate (this=0x7fffe011b340, renderer=0x7fff8a35b9a0) at ../Source/WebCore/accessibility/AXObjectCache.cpp:271 271 ../Source/WebCore/accessibility/AXObjectCache.cpp: No such file or directory. in ../Source/WebCore/accessibility/AXObjectCache.cpp
+ Trace 228125
Please disable accessibility in your system to avoid such crash.
Dear Akhil, While it can be a workaround for current breakage, taking accessibility out in general would be a bad idea in general.
(In reply to comment #4) > taking accessibility out in general That's up to your distribution / compile options. We prefer to enable options in test builds to see if options work.
(In reply to comment #5) > (In reply to comment #4) > > taking accessibility out in general > > That's up to your distribution / compile options. > We prefer to enable options in test builds to see if options work. What do you mean exactly? Accessibility in webkitgtk is not supported and should be disabled?
(In reply to comment #3) > Please disable accessibility in your system to avoid such crash. I guess we all agree that this is not the suggested path to follow from the ephy/webkit team, so there's no need to continue arguing further from there.
(In reply to comment #6) > (In reply to comment #5) > > (In reply to comment #4) > > > taking accessibility out in general > > > > That's up to your distribution / compile options. > > We prefer to enable options in test builds to see if options work. > > What do you mean exactly? Accessibility in webkitgtk is not supported and > should be disabled? Some people has spent a lot of work to get WebKitGTK accessibility support in a good shape. Although it doesn't cover as much use cases as Firefox (ie ARIA), it should cover the basic use case, and some people felt that for those cases using Orca to interact with those cases works smoothly. IMHO, this is just a crash in a really specific environment, and not the base to conclude that accessibility in webkitgtk is not supported at all.
This appears to have been fixed. I cannot reproduce the problem any longer (using GNOME 3.4 and 3.6).