I can consistently reproduce the bug by visiting this page

http://www.steadfastequipment.com/

I'm running the pure64 port of unstable with FF 1.0.6. The stack trace I get 
when visiting the above site is:

#0  0x00002aaaab5b7d25 in raise () from /lib/libpthread.so.0
#1  0x0000000000cf8954 in nsIDirectoryServiceProvider2::GetIID ()
#2  <signal handler called>
#3  0x00002aaab0dab2bb in NPP_SetWindow () 
from /usr/lib/mozilla/plugins/kaffeineplugin.so
#4  0x00002aaab0dab799 in Private_SetWindow () 
from /usr/lib/mozilla/plugins/kaffeineplugin.so
#5  0x000000000062d585 in nsISupportsArray::GetIID ()
#6  0x00000000006460cf in nsIDirectoryServiceProvider::GetIID ()
#7  0x000000000063ad1f in nsISupportsArray::GetIID ()
#8  0x00000000008fd826 in nsIComponentRegistrar::GetIID ()
#9  0x00000000008fed7c in nsIComponentRegistrar::GetIID ()
#10 0x00000000008f6d64 in nsIComponentRegistrar::GetIID ()
...

I've also caught another stack trace from a page that doesn't have any fancy 
media on it (just plain old HTML).

#0  0x00002aaaab5b7d25 in raise () from /lib/libpthread.so.0
#1  0x0000000000cf8954 in nsIDirectoryServiceProvider2::GetIID ()
#2  <signal handler called>
#3  0x00000000006201de in nsISupportsArray::GetIID ()
#4  0x000000000061cae1 in nsISupportsArray::GetIID ()
#5  0x000000000051321a in nsISupportsPRUint32::GetIID ()
#6  0x0000000000518a20 in nsISupportsPRUint32::GetIID ()
#7  0x00000000004b9679 in nsIStreamBufferAccess::GetIID ()
#8  0x00000000004b9baa in nsIStreamBufferAccess::GetIID ()
#9  0x00002aaaab0e28d5 in nsInputStreamReadyEvent::EventHandler () 
from /usr/lib/mozilla-firefox/libxpcom.so
#10 0x00002aaaab0f74c9 in PL_HandleEvent () 
from /usr/lib/mozilla-firefox/libxpcom.so
#11 0x00002aaaab0f7c68 in PL_ProcessPendingEvents () 
from /usr/lib/mozilla-firefox/libxpcom.so
#12 0x00002aaaab0f95eb in nsEventQueueImpl::~nsEventQueueImpl () 
from /usr/lib/mozilla-firefox/libxpcom.so
#13 0x000000000065d272 in nsIDirectoryServiceProvider::GetIID ()
#14 0x00002aaaac46ae5b in g_vasprintf () from /usr/lib/libglib-2.0.so.0
...

Reply via email to