User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; de-AT; rv:1.6) Gecko/20040113 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; de-AT; rv:1.6) Gecko/20040113 First: no, the mentioned page isn't a crasher. But I found 'mine' there. I tried to have a look on the mentioned problem, so I marked the URL (http://www.mozilla.org/projects/calendar/holidays.html), took it with the mouse and dragged it to the tab-bar. But I didn't notice I didn't get the whole text. I missed the 'h'. So I got a message box, saying 'ttp isn't a valid protocol' (ok, I got 'ttp ist kein registriertes Protokoll' as I'm using the austrian/german localisation) and the next thing happening is s prue crash. OS X tells me, mozilla.bin is terminated unexpectedly. I repeated it once: again, same symptoms. Reproducible: Always Steps to Reproduce: 1. dragging incomplete URL to tab-bar (missing char in the protocol-header) Actual Results: 1. message box 'ttp isn't a registered protocol' 2. a short moment later mozilla is gone. Expected Results: let me take notice, close the message box an try again. While doing so the mail client had been working in a shrunk window. Doon't know if this matters. And I'm sorry for not having time to do more tests - I got W2K-System with a broken mainboard and important data on its's near by 1TB disk space :-( BTW: who will kill Windown? There in no bug-dows. The text I'd have to send there would be realy much larger …
i see no crash, but get the alert twice: It immediately reappears after being dismissed the first time. Current trunk, Linux
WFM using Mac 1.7b. Franz, the 20040113 build is a bit old for bug reporting purposes. Please try to reproduce the problem using a current nightly build.
This build is a bit old? Ok, I know there is no sleep at mozilla town ;-) But it's the official 1.6 final release (or do you update this without notification?) so I think it should be 'official' fixed - if it's a mozilla problem. But I have a problem: as I mentioned before I got trouble with the Desktop. As long it isn't set up fully my iBook is my procuction system. So it will last some days before I can upgrade mozilla there. I will do, but if someone could do the tests right now he could save you (not me - actually I have no time for 'playing around', damn Windows eats it up fully :-/) some time. Franz
I can't reproduce this with either 1.7b or 20040323 Firefox/0.8.0+ on FreeBSD.
Ok, been lucky - some things were done faster than I thought :-) So I updated mozilla: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7b) Gecko/20040323 But sadly it keeps crashing when I retry this action :-( I think it takes a bit longer from the moment of the 'ist not a'-dialog till the shutdown, but it still acts so. Franz
Franz, can you attach a crash log?
Created attachment 144759 [details] Crash reporter log file Sure I do, here it is (am I right if I think crash reporter is always on beneath panther? Didn't have to enable anything, didn't see some switch at all). I hope you'll have some fun with it :-/ Franz
--> XP Apps: Drag and Drop. See also bug 186976 and bug 198150.
Assignee: tabbed-browser → firefox
Component: Tabbed Browser → XP Apps: Drag and Drop
QA Contact: pmac
Summary: crash when dragging a (broken!) URL to the tab-bar → crash when dragging a (broken!) URL to the tab-bar [@ nsDragHelperService::Drop]
I can't reproduce this with Mozilla 2004040505 on mac os 10.2.8. I do get the alert twice, though.
Confirmed using Mozilla-Mac/2004041406. However, comment 8 is accurate. This bug, as well as bug 198150, share the same stack as bug 186976, so all three are probably different manifestations of the same problem.
Oops, setting NEW.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Created attachment 172118 [details] Stack Trace This is seemingly still in. I independently rediscovered and retraced the steps of the original report and got what I believe to be the same crash. I enclose a stack trace from the Jaguar crash reporter. I will see if I can catch this in the debugger.
(In reply to comment #12) > This is seemingly still in. I independently rediscovered and retraced the > steps of the original report and got what I believe to be the same crash. I should have said: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b) Gecko/20050122 Firefox/1.0+ (Today's build using standard methods)
Status: NEW → RESOLVED
Last Resolved: 13 years ago
OS: MacOS X → All
Hardware: Macintosh → All
Resolution: --- → WONTFIX
Version: Trunk → Other Branch
Reporter, can you please explain why you marked this as wontfix? No one has said anything about wontfix in here...
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Assignee: bross2 → nobody
Status: REOPENED → NEW
QA Contact: pmac
can you reproduce using FF 3.5 beta? WFM, no crash with Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b4pre) Gecko/20090314 Shiretoko/3.1b4pre (.NET CLR 3.5.30729)
QA Contact: drag-drop
WFM in FF 3.0 on OS X 10.5. Sounds like it only affects the older builds.
WFM using Firefox trunk on OS X 10.5. I even tried doing wacky stuff while the dialog was up (switching to another window; dragging another bad URL) inspired by bug 198150. Fun fact: you can't initiate another drag, even from a third browser window, until you dismiss the dialog.
Status: NEW → RESOLVED
Last Resolved: 13 years ago → 9 years ago
Resolution: --- → WORKSFORME
Crash Signature: [@ nsDragHelperService::Drop]
You need to log in before you can comment on or make changes to this bug.