Created attachment 1250788 [details] Crash backtrace. Description of problem: Epiphany randomly crashes while I browse sechat.org. Version-Release number of selected component (if applicable): Web 3.22.6 How reproducible: Login in to sechat.org, or may be any other Diaspora* pod. Browse around, click links, check notifications. Actual results: Crash. Expected results: No crash. Additional info: Back trace is attached.
Memory corruption. If you can reproduce, it would be really awesome if you could catch it in valgrind.
(In reply to Michael Catanzaro from comment #1) > Memory corruption. If you can reproduce, it would be really awesome if you > could catch it in valgrind. Can you give me instructions how to catch it in valgrind?
Just 'valgrind epiphany' should be enough, since it's a UI process issue. Ifval
(In reply to Michael Catanzaro from comment #3) > Just 'valgrind epiphany' should be enough, since it's a UI process issue. > Ifval Sorry, I guess I was planning to write something else there at the end. Ignore that last bit!
Still can not catch fault in fedora, but got crash with valgrind in debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855261#10
The valgrind log shows a different, unrelated crash (from an X window system error). I wonder if that one might have been fixed in 2.14.5. Please wait for that update and see if you can still reproduce it then; if so, we should report it upstream (on WebKit Bugzilla). Back to this issue. The problem here is the memory corruption could be in Epiphany, or WebKit (most likely), or any dependency: we really have no clue unless we can catch it in valgrind. So nothing actionable yet, I'm afraid.
Ca not reproduce anymore. Closing.