Epiphany window closes very slowly.

Thanks for your bug. Does it happen if you open open epiphany and close it after loading one page or just after extensively using it? What version of Ubuntu do you use? Does that happen on fast or slow boxes? Does you use some extensions non activated by default? Could you get a backtrace using gdb of what it's doing then?
before closing it
- gdb -p $(pidof epiphany)
(gdb) continue

then close it, and when it's using the CPU switch to gdb and hit Ctrl-C on you keyboard, then type "thread apply all bt" and copy that to a comment

The pause normally occurs after long-term use of the browser.

I am using Dapper Beta with all current updates applied. I have been using Dapper for about 2 months, and this bug has just manifested itself within the past week or so.

It occurs on an AMD Turion 64 at 2.0 GHz with 2GB RAM, a Pentium-M 1.7 GHz with 1GB RAM, and an AMD Athlon at 1.8 GHz with 750MB RAM. All machines are Dapper and up to date. The only difference is the Turion which is running the 64 bit version.

The browser extensions are in the fully default setup.

Here is the backtrace from the 64 bit version:

Thread 8 (Thread 1082132832 (LWP 26976)):
#0 0x00002aaaab1f8e22 in poll () from /lib/libc.so.6
#1 0x00002aaaab0258df in PR_Poll () from /usr/lib/libnspr4.so
#2 0x00002aaab23e3690 in NSGetModule ()
   from /usr/lib/firefox/components/libnecko.so
#3 0x00002aaab23e3de3 in NSGetModule ()
   from /usr/lib/firefox/components/libnecko.so
#4 0x00002aaab0a5179c in nsIThread::IsMainThread ()
   from /usr/lib/firefox/libxpcom_core.so
#5 0x00002aaaab026e9c in PR_Select () from /usr/lib/libnspr4.so
#6 0x00002aaab02da0fa in start_thread () from /lib/libpthread.so.0
#7 0x00002aaaab201ce2 in clone () from /lib/libc.so.6
#8 0x0000000000000000 in ?? ()

Thread 7 (Thread 1090525536 (LWP 26978)):
#0 0x00002aaab02dcc8f in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/libpthread.so.0
#1 0x00002aaaab021c0d in PR_Lock () from /usr/lib/libnspr4.so
#2 0x00002aaaab021f7d in PR_WaitCondVar () from /usr/lib/libnspr4.so
#3 0x00002aaab0a53b10 in NS_NewThread ()
   from /usr/lib/firefox/libxpcom_core.so
#4 0x00002aaab0a5179c in nsIThread::IsMainThread ()
   from /usr/lib/firefox/libxpcom_core.so
#5 0x00002aaaab026e9c in PR_Select () from /usr/lib/libnspr4.so
#6 0x00002aaab02da0fa in start_thread () from /lib/libpthread.so.0
#7 0x00002aaaab201ce2 in clone () from /lib/libc.so.6
#8 0x0000000000000000 in ?? ()

Thread 6 (Thread 1098918240 (LWP 26979)):
#0 0x00002aaab02dcc8f in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/libpthread.so.0
#1 0x00002aaaab021c0d in PR_Lock () from /usr/lib/libnspr4.so
#2 0x00002aaaab021f7d in PR_WaitCondVar () from /usr/lib/libnspr4.so
#3 0x00002aaab23eee73 in NSGetModule ()
   from /usr/lib/firefox/components/libnecko.so
#4 0x00002aaab23ef75c in NSGetModule ()
   from /usr/lib/firefox/components/libnecko.so
#5 0x00002aaaab026e9c in PR_Select () from /usr/lib/libnspr4.so
#6 0x00002aaab02da0fa in start_thread () from /lib/libpthread.so.0
#7 0x00002aaaab201ce2 in clone () from /lib/libc.so.6
#8 0x0000000000000000 in ?? ()

Thread 5 (Thread 1107310944 (LWP 26980)):
#0 0x00002aaab02dcc8f in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/l#1 0x00002aaaab021c0d in PR_Lock () from /usr/lib/libnspr4.so
#2 0x00002aaaab021f7d in PR_WaitCondVar () from /usr/lib/libnspr4.so
#3 0x00002aaab23c24df in NSGetModule ()
   from /usr/lib/firefox/components/libnecko.so
#4 0x00002aaaab026e9c in PR_Select () from /usr/lib/libnspr4.so
#5 0x00002aaab02da0fa in start_thread () from /lib/libpthread.so.0
#6 0x00002aaaab201ce2 in clone () from /lib/libc.so.6
#7 0x0000000000000000 in ?? ()...

Do you still see the problem in the Dapper release? Do you get any messages in the terminal?

I do believe this is fixed. I do not notice it with the final
release. Thanks for the followup.

- Rod

On Aug 7, 2006, at 4:44 AM, Daniel Holbach wrote:

> Do you still see the problem in the Dapper release? Do you get any
> messages in the terminal?
>
> --
> Epiphany window closes very slowly.
> https://launchpad.net/bugs/41892
>

Glad to hear it's fixed for you. Thanks for following up.