Steps to reproduce: 1. Visit the URL listed. 2. Scroll to the bottom. 3. Click in the middle of the Yiddish text and drag up, selecting the text past the "Yiddish" title. Mozilla will hang. It's stuck in code like this: #0 nsLineIterator::Init (this=0x821c808, aLines=@0x425d11c0, aRightToLeft=-1073755492) at nsLineBox.cpp:586 #1 0x424c94a4 in nsFrameList::GetNextVisualFor (this=0xbfffcac4, aFrame=0x420154f0) at nsFrameList.cpp:571 #2 0x424cb015 in nsVisualIterator::Next (this=0x42d47090) at nsFrameTraversal.cpp:691 #3 0x42358957 in nsFrame::GetFrameFromDirection (this=0x82762ac, aPresContext=0x81c1ec8, aPos=0xbfffd230) at nsFrame.cpp:3759 #4 0x423bfb7e in nsTextFrame::PeekOffset (this=0x82762ac, aPresContext=0x81c1ec8, aPos=0xbfffd230) at nsTextFrame.cpp:4237 #5 0x415b56fd in nsSelection::VisualSequence (this=0x81c4918, aPresContext=0x81c1ec8, aSelectFrame=0x82762ac, aCurrentFrame=0x8275e08, aPos=0xbfffd230, aNeedVisualSelection=0xbfffd16c) at nsSelection.cpp:1834 #6 0x415b7043 in nsSelection::VisualSelectFrames (this=0x81c4918, aPresContext=0x81c1ec8, aCurrentFrame=0x8275e08, aPos=0xbfffd230) at nsSelection.cpp:2153 #7 0x415b8a1c in nsSelection::HandleDrag (this=0x81c4918, aPresContext=0x81c1ec8, aFrame=0x8275e08, aPoint=@0xbfffd7b8) at nsSelection.cpp:2609 #8 0x42351db4 in nsFrame::HandleDrag (this=0x8275e08, aPresContext=0x81c1ec8, aEvent=0xbfffd7b0, aEventStatus=0xbfffd584) at nsFrame.cpp:1385 #9 0x4234f336 in nsFrame::HandleEvent (this=0x8275e08, aPresContext=0x81c1ec8, aEvent=0xbfffd7b0, aEventStatus=0xbfffd584) at nsFrame.cpp:717 #10 0x423a84e4 in PresShell::HandleEventInternal (this=0x81c32a0, aEvent=0xbfffd7b0, aView=0x821cf50, aFlags=1, aStatus=0xbfffd584) at nsPresShell.cpp:6015 #11 0x423a7fd4 in PresShell::HandleEvent (this=0x81c32a0, aView=0x821cf50, aEvent=0xbfffd7b0, aEventStatus=0xbfffd584, aForceHandle=1, aHandled=@0xbfffd544) at nsPresShell.cpp:5923 #12 0x4261b399 in nsViewManager::HandleEvent (this=0x81c29f8, aView=0x821cf50, aEvent=0xbfffd7b0, aCaptured=1) at nsViewManager.cpp:2003 #13 0x4260ef49 in nsView::HandleEvent (this=0x821cf50, aVM=0x81c29f8, aEvent=0xbfffd7b0, aCaptured=1) at nsView.cpp:300 #14 0x4261ac87 in nsViewManager::DispatchEvent (this=0x81c29f8, aEvent=0xbfffd7b0, aStatus=0xbfffd680) at nsViewManager.cpp:1838 #15 0x4260e7f2 in HandleEvent (aEvent=0xbfffd7b0) at nsView.cpp:80 #16 0x41a2c956 in nsWidget::DispatchEvent (this=0x821cc98, aEvent=0xbfffd7b0, aStatus=@0xbfffd73c) at nsWidget.cpp:1382 #17 0x41a2c56e in nsWidget::DispatchWindowEvent (this=0x821cc98, event=0xbfffd7b0) at nsWidget.cpp:1270 #18 0x41a2ca17 in nsWidget::DispatchMouseEvent (this=0x821cc98, aEvent=@0xbfffd7b0) at nsWidget.cpp:1409 #19 0x41a2d087 in nsWidget::OnMotionNotifySignal (this=0x821cc98, aGdkMotionEvent=0xbfffd830) at nsWidget.cpp:1643 #20 0x41a330d9 in nsWindow::HandleGDKEvent (this=0x821cc98, event=0x8176488) at nsWindow.cpp:1577 #21 0x41a2472a in dispatch_superwin_event (event=0x8176488, window=0x821cc98) at nsGtkEventHandler.cpp:943 #22 0x41a24259 in handle_gdk_event (event=0x8176488, data=0x0) at nsGtkEventHandler.cpp:764 #23 0x403a3d7f in gdk_event_dispatch () from /usr/lib/libgdk-1.2.so.0 #24 0x403d7773 in g_main_dispatch () from /usr/lib/libglib-1.2.so.0 #25 0x403d7d39 in g_main_iterate () from /usr/lib/libglib-1.2.so.0 #26 0x403d7eec in g_main_run () from /usr/lib/libglib-1.2.so.0 #27 0x402f2333 in gtk_main () from /usr/lib/libgtk-1.2.so.0 #28 0x08049fc2 in main (argc=1, argv=0xbfffdb74) at TestGtkEmbed.cpp:208 #29 0x404fc627 in __libc_start_main (main=0x8049e10 <main>, argc=1, ubp_av=0xbfffdb74, init=0x8049764 <_init>, fini=0x804c850 <_fini>, rtld_fini=0x4000dcc4 <_dl_fini>, stack_end=0xbfffdb6c) at ../sysdeps/generic/libc-start.c:129 (gdb) k

This sounds like a dupe of bug 98440

It hangs using 2002021403 build on WinXP. Setting OS to ALL: Looks like a selection issue: Reassigning to mjudge

setting the priority to P3

hmmm goingwith BIDI on this one.

reassigning

I think this should have been fixed by the checkin to bug 76190, but I can't reproduce the hang in builds either before or after that checkin. Can you retest?

Chris, are you still seeing this?

Nope, this seems to have been fixed.