epiphany crashes often on tab closing.

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a '.crash' file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

 If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

 If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.
 I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

the valgrind log has no error, did you close all the open dialog before running to command? it looks like it just used a running instance rather than starting a new one using valgrind

Sure new instance. I have now installed and started apport. i got a response that epiphany-gecko crashed but a dialog told be that I have not enough RAM to send you a bug report. :-(

I will try again after a reboot.

No sorry, hwtas what i get in german:
"""
Das Programm "epiphany-gecko" wurde unerwartet beendet

Ihr Rechner verfügt nicht über ausreichend Arbeitsspeicher, um das Problem näher zu analysieren und einen Problembericht an die Entwickler zu senden.
"""

The application "epiphany-gecko" was killed unexpectedly. You computer does not have enough memory to analyze this problem more thoroughly and send a problem report to the developers.

I would say a bug tool which requires a minimum RAM is quite unusable because low RAM can be one potential cause - so I never can get to the point tothe cause if the bug program can not analyze the situation.

$ free -m
             total used free shared buffers cached
Mem: 367 360 6 0 2 71
-/+ buffers/cache: 287 80
Swap: 478 53 424

attaching another crash file

could you get a stacktrace using gdb as described on http://wiki.ubuntu.com/DebuggingProgramCrash?

The link you have doesnt tell me much on how to do it. I even installed nemiver as a GUI but I could not find out how to save a debug log. So I just ran strace and hope that the log I made gives some more information.

the strace logs are usually not useful, you need to use gdb and get a stacktrace, the wiki page steps have a pointer to the page which describe how to get a backtrace, are you sure you read it correctly?

Sure. The only line that contains the 3 letters gdb is this:
"apt-get update; apt-get install gdb apport" . Now I know what you meant - the actual page is https://wiki.ubuntu.com/Backtrace - so it does not contain the three letter "gdb" - I did not look at that because I was sure it cant have anything about gdb (otherwise it would be called differently).... will try that

Ok, gdb seems to keep epiphany from crashing a bit because I had to try much harder before it crashed. What I did was going to youtube, open a bunch of tabs and then closing all again for some time. Attached is the backtrace.

"#1 0xae09a5ae in ?? () from /usr/lib/flashplugin-nonfree/libflashplayer.so"

the issue is another closed source adobe flash plugin issue

One thing I like to add is that this only happens in epiphany and not in Firefox.

> the issue is another closed source adobe flash plugin issue

Is shrugging off responsibility because the flash plugin is proprietary the best attitude?

Somehow Firefox manages to use the flash plugin without crashing.

Is this symptom still reproducible in 9.04 alpha 3 (http://cdimages.ubuntu.com/releases/9.04/alpha-3/)?

Well no. Its funny that users are expected to try out Alpha software. I know it often only makes sense to try out with latest changes - but to suggest a user to use alpha software is just dangerous. If I would I would get other problems and then the feedback why on earth I chose to use alpha and that I then have to just live with it. I am primarily using Firefox now. I think anybody running Epiphany and this alpha release can take on this tests. I will not test alpha.

Yes, theres still that problem in alpha 5.

This is still happening in a fully updated 9.04