SPants Posted October 28, 2008 Report Share Posted October 28, 2008 I've restarted Firefox three times in the last 15 minutes, because each time it crashed immediately upon my downloading of new torrent info from isohunt - as soon as the firefox torrent-info download progress bar hits 100%, I get the "firefox has encountered a problem and needs to close" box. The torrents, though, do start the normal utorrent process of downloading, but Firefox is dead then. It's done this the last five-ish times I have started a new torrent as above. WTF? Link to comment Share on other sites More sharing options...
thelittlefire Posted October 28, 2008 Report Share Posted October 28, 2008 ...uTorrent doesn't do anything to firefox. It's actually the reverse, when you launch from firefox, uTorrent.exeThere is no correlation between downloading the .TORRENT, uTorrent, and Firefox crashing. Are you sure you don't have plugin incompatibilities? When you launch uTorrent.exe that way, can you create and paste a Process Explorer DLL list for utorrent.exe ? Link to comment Share on other sites More sharing options...
SPants Posted October 29, 2008 Author Report Share Posted October 29, 2008 littlefire,Thanks for the reply. Can you give more info on how to "...create and paste a Process Explorer DLL list for utorrent.exe ..."? I have process explorer running now, but not sure how to configure it give you the info you need - presumably from events that occur when I next crash FF by starting a new torrent, which should be totally predictable. Link to comment Share on other sites More sharing options...
thelittlefire Posted October 29, 2008 Report Share Posted October 29, 2008 Well, Process Explorer is like... think of it as a super "Task Manager". It even has the ability to show Task Manager Instructions are in the sticky http://forum.utorrent.com/vewtopic.php?d=15992 but basically all you need to do is highlight uTorrent.exe, Ctrl-D, Save a logfile (Ctrl-A), paste its contents into this thread. However if I may when firefox crashes before you close the window, could you go to it's properties in Process Explorer (double click should work), there is a place in the properties to show "call stack"... it will list all operations currently pending when the crash occurred. I'm thinking that's the most direct way to investigate the problem... whether or not utorrent.exe is to blame that list may help. or not. I don't think you can copy-paste the text, so I'd use Alt-PrintScreen to make a picture, save it, upload to http://imageshack.us and use the "forum(1) bbcode" in this thread as well. Link to comment Share on other sites More sharing options...
SPants Posted October 30, 2008 Author Report Share Posted October 30, 2008 Kristy,Thanks again. I was about to duplicate the FF-crash and figure out which of the "stack" logs would be of interest, and suddenly found that my (wireless) ISP connection wouldn't stay up for more than about a minute, so I set aside the effort to start a torrent. Twelve hours later, the fix for the wireless connection dropouts seems to have been to disable some mysterious and/or unused network connections - my ISP reported that on their end, they were seeing two different IP addresses attempting to connect, or something like that. Anyway, now that THAT is fixed, utorrent has (at least once now) /not/ caused FF to crash on starting a new torrent. I'm hoping it will remain stable now.Somehow I am sure those two issues were related, but maybe I'd best not try to wrap my tiny little brain around that.Mahalo,Dave Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.