Simple HTML button binding crashes Mozilla

RESOLVED INVALID

Status

()

Core
XBL
P3
normal
RESOLVED INVALID
18 years ago
18 years ago

People

(Reporter: Taras Tielkes, Assigned: David Hyatt)

Tracking

({crash, testcase})

Trunk
Future
x86
Other
crash, testcase
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(3 attachments)

(Reporter)

Description

18 years ago
1) I'm just staring with XBL
2) Binding "keypress" to an HTML input button is probably meaningless
3) I didn't dig too deep to find a minimal testcase

Adding the second binding to the XBL file and binding it to the input control 
seems to cause a crash on document load time. Using 15/9 build on WinNT.
(Reporter)

Comment 1

18 years ago
Created attachment 14794 [details]
Testcase (XBL part)
(Reporter)

Comment 2

18 years ago
Created attachment 14795 [details]
Testcase (HTML part)
(Reporter)

Comment 3

18 years ago
Created attachment 14797 [details]
Updated testcase (HTML part)
(Reporter)

Comment 4

18 years ago
I can't reproduce the crash with the uploaded testcases.

My guess is that no longer using relative paths of the form "url
(myxbl.xml#test)" prevents the bug from showing.

I have uploaded the testcase files, with relative paths, to a free hosing page 
at: http://pakkapakka.webhostme.com/myxbl.html
(Reporter)

Comment 5

18 years ago
Behaviour seen at the pakkapakka url:

1) Sometimes the browser crashes immediately at document load time.\
2) Sometimes the document is loaded without crashing, but pressing the button 
will procuce a Visual C++ Runtime warning (pure virtual function call).
(Reporter)

Updated

18 years ago

Comment 6

18 years ago
linux 2000091508.
Crash on loading:
error in console->
JavaScript error: 
 line 0: uncaught exception: [Exception... "Component returned failure code:
0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPref.GetBoolPref]"  nsresult: "0x8000ffff
(NS_ERROR_UNEXPECTED)"  location: "JS frame ::
chrome://navigator/content/navigator.js :: URLBarBlurHandler :: line 2137" 
data: no]

Sometimes I get the same error also for line 5.

Stack:
Program received signal SIGSEGV, Segmentation fault.
0x405bf3e0 in NSGetModule () from /root/package/components/libnecko.so
(gdb) bt
#0  0x405bf3e0 in NSGetModule () from /root/package/components/libnecko.so
#1  0x405bd678 in NSGetModule () from /root/package/components/libnecko.so
#2  0x405a6181 in NSGetModule () from /root/package/components/libnecko.so
#3  0x4057d004 in NSGetModule () from /root/package/components/libnecko.so
#4  0x4057c8b0 in NSGetModule () from /root/package/components/libnecko.so
#5  0x400bf163 in PL_HandleEvent () from /root/package/./libxpcom.so
#6  0x400bf083 in PL_ProcessPendingEvents () from /root/package/./libxpcom.so
#7  0x400bfddd in nsEventQueueImpl::ProcessPendingEvents ()
   from /root/package/./libxpcom.so
#8  0x406fa24f in NSGetModule () from /root/package/components/libwidget_gtk.so
#9  0x406fa00d in NSGetModule () from /root/package/components/libwidget_gtk.so
#10 0x4089baca in g_io_unix_dispatch () from /usr/lib/libglib-1.2.so.0
#11 0x4089d186 in g_main_dispatch () from /usr/lib/libglib-1.2.so.0
#12 0x4089d751 in g_main_iterate () from /usr/lib/libglib-1.2.so.0
#13 0x4089d8f1 in g_main_run () from /usr/lib/libglib-1.2.so.0
#14 0x407c25b9 in gtk_main () from /usr/lib/libgtk-1.2.so.0
#15 0x406fa73c in NSGetModule () from /root/package/components/libwidget_gtk.so
#16 0x4045a4ba in inflate_mask ()
   from /root/package/components/libnsappshell.so
#17 0x804db37 in JS_PushArguments ()
#18 0x804df96 in JS_PushArguments ()
#19 0x4025b9cb in __libc_start_main (main=0x804de8c <JS_PushArguments+11368>, 
    argc=2, argv=0xbffff634, init=0x804ada4 <_init>, fini=0x805361c <_fini>, 
    rtld_fini=0x4000ae60 <_dl_fini>, stack_end=0xbffff62c)
    at ../sysdeps/generic/libc-start.c:92

However I don't know if this crash is the same of the initial bug report as it
happens before I can press the button.
(Assignee)

Updated

18 years ago
Status: NEW → ASSIGNED
Target Milestone: --- → Future
(Assignee)

Comment 7

18 years ago
Your Web server is not set up to return the correct MIME type for the XML file
(text/xml).
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.