tested using opt comm bits 2000.03.09.13 on linux. 1. bring Open Web Location dialog. 2. enter the above URL, select open in New Composer window radio button. 3. click Open. result: outline of Composer window is drawn, then browser crashes. expected: shouldn't crash; should happily load page in a new composer window. note that this isn't a problem if i go to File > Edit Page (currently File > d ;-) talkback info: http://cyclone/reports/incidenttemplate.CFM?reportID=124&style=0&tc=51&cp=1&ck1=SUser+email+address&cd1=%25sairuh%40netscape%2Ecom%25&co1=like&bbid=6584561 Trigger Type: Program Crash Trigger Reason: SIGSEGV: Segmentation Fault: (signal 11) Call Stack: (Signature = libwidget_gtk.so + 0x353df (0x4153f3df) 04681c89) libwidget_gtk.so + 0x353df (0x4153f3df) libwidget_gtk.so + 0x36afb (0x41540afb) libwidget_gtk.so + 0x3c1d7 (0x415461d7) libgfx_gtk.so + 0x142b0 (0x416282b0) libwidget_gtk.so + 0x4018e (0x4154a18e) libwidget_gtk.so + 0x3aa11 (0x41544a11) libwidget_gtk.so + 0x3ab9f (0x41544b9f) libwidget_gtk.so + 0x3a8e9 (0x415448e9) libglib-1.2.so.0 + 0x10ba9 (0x405a4ba9) libglib-1.2.so.0 + 0xfbe6 (0x405a3be6) libglib-1.2.so.0 + 0x101a1 (0x405a41a1) libglib-1.2.so.0 + 0x10341 (0x405a4341) libgtk-1.2.so.0 + 0x8c209 (0x404cb209) libwidget_gtk.so + 0x255aa (0x4152f5aa) libnsappshell.so + 0x140e2 (0x40f580e2) mozilla-bin + 0x2f2c (0x0804af2c) mozilla-bin + 0x324c (0x0804b24c) libc.so.6 + 0x181eb (0x4021d1eb)
came from discussion in bug 24903... danm, have you seen this occur on platforms other than linux? i haven't been able to repro on winNT [2000.03.09.08 opt comm bits] or macOS [2000.03.09.13 opt non-comm bits].
This problem seems confined to only Linux among the Three. Note this is almost certainly the same problem, and therefore the same bug, as 24903.
same even though the stack info is different? just curious --thanks!
Putting on PDT+ radar for beta1 to disable, similar to 24903.
If this is the same as bug #24903, then why the Hell do I have the bug?
Yes, the stack traces are different enough that it's worth keeping both open. But it's likely that the real problem is a set of conditions created way before anything mentioned in the stack traces. A note of clarification about leger's comment is in order here, as in the sibling bug. The most likely way to disable this functionality is to change the two radio buttons to "Don't select me" and "Don't select me either". Or maybe disable the OK button, leaving only Cancel.
unlike sibling bug 24903, this is a regression w/respect to 4.72 (on linux). ah, more keywords.
Can I have an update on the status of this bug? Progress? plans? comments? Thanks, Jim
Feeling nervous about this bug... I decided to add mscott and pav to the fray (cc list). This sure sounds a lot like 24903. Both involve ONLY linux. Both involve new browser windows. We need to know if there is a work-around, and we can grey out an access to this functionality to ship beta. If we can't, then this bug becomes a MUST FIX. Comments??? Thanks, Jim
You should be nervous about this bug. The root cause is mysterious and awful. I still can't name it. But the crash can be shooed off by application of clever hunch. This is fixed on the trunk. I'll move it over to M14 next week, after I manage to thread all the appropriate bureaucratic tangles.
note: bits came from the 2000.03.13.03.M15-nb1b branch.
Branch works like trunk now.
works now; verif using linux [2000.03.13.19-nb1b, opt comm].