Fetch Softworks

Machine Freezes after "View as Text" (13 posts)

• Started 22 years ago by mstielau
• Latest reply 22 years ago from mstielau

• mstielau Member

  I use Fetch to maintain web sites on several different servers. There is one server in particular that causes a problem for Fetch when I use "View as Text" on the contextual menu. Fetch displays the file, then immediately freezes my Mac, requiring a forced restart. This problem seems to only happen with this particular server.

  I hand-copied the Transcript of the session off the screen before restarting (below). I have tried trashing prefs, cache, and shortcuts, with no luck.

  NEW INFORMATION (11/05/01) I guess this isn't limited to the "View as Text" command. My Mac also locks up when attempting to download a file either by double-clicking the file name in Fetch's window, or by using the "Get File" command from the contextual menu. This problem does not occur when using Fetch 3.0.3 with this server. The problem also does not occur in Fetch 4 when using the "Edit with BBEdit" command in the contextual menu.

  - Michael

  Transcript:

  NOOP
  200 NOOP Command Successful
  SIZE .bash_history
  213 577984125663708077
  MDTM .bash_history
  213 20011026171955
  PASV
  227 Entering Passive Mode (208,234,15,226,238,187)
  RETR .bash_history
  150 Opening ASCII mode data connection for '.bash_history' (816 bytes)
  226 Transfer Complete

  ** At this point, it displays the file, then immediately freezes the machine. **

  [This message has been edited by mstielau (edited 11-05-2001).]

  [This message has been edited by mstielau (edited 11-05-2001).]

  Posted 22 years ago #

• Jim Matthews Administrator

  That's very strange. Do you know what sort of server this is? It should say in response to the SYST command, earlier in the transcript.

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 22 years ago #

• mstielau Member

  Here's the section of the transcript you requested.

  - Michael

  SYST
  215 UNIX Type: L8 Version: LINUX

  Posted 22 years ago #

• Jim Matthews Administrator

  Do you have any trouble when you try to download files from ftp.fetchsoftworks.com (leave User ID and Password fields blank)?

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 22 years ago #

• mstielau Member

  There was only one file (fetchicon.gif) to download at that address, and it downloaded with no problem. But it is text files that are causing the lockup. Can you put some plain text files there for me to try?

  - Michael

  Posted 22 years ago #

• Jim Matthews Administrator

  Ok, I've put up a couple of text files (one small, one large).

  Jim Matthews
  Fetch Softworks

  Posted 22 years ago #

• mstielau Member

  I experienced no similar problem with either of those files. I tried both "View as Text" and "Get" with both of them.

  (My machine did lock up when GETting the larger one, but I was doing other things while Fetch was downloading in the background, so it's not related to the problem I originally described.)

  If you're so inclined, you can try this for yourself and see if it happens to you too. I've created an ftp account for you on the server in question and will send the login information to you via the form on your feedback page.

  I tried it again - just to make sure - and sure enough, Fetch 3.0.3 works without a hitch, but Fetch 4 locks up my Mac.

  - Michael

  [This message has been edited by mstielau (edited 11-07-2001).]

  Posted 22 years ago #

• Jim Matthews Administrator

  Thanks -- having the test account helped me track down the problem.

  The problem seems to be due to two bugs. First, the server is responding incorrectly to the SIZE command (which is supposed to return the size of the file). You can see this in the transcript you posted above:

  SIZE .bash_history
  213 577984125663708077

  So the server is saying that the file is 577,984,125,663,708,077 bytes long, which is nonsense. Unfortunately, when Fetch goes to display this nonsense number it only reserves 15 characters of space -- but the nonsense number needs 23 (including commas). The result is corrupted memory and a freeze or crash.

  Fetch 3.0.3 does not have the problem because it does not use the SIZE command.

  I will fix the Fetch bug in the next release. You could also contact the server administrator about installing an update that fixes the SIZE command.

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 22 years ago #

• mstielau Member

  Glad having the test account helped. Teamwork! :-)

  Good troubleshooting on your part. I'll contact the hosting company and let them know of the problem. And I'll point them to this thread for details.

  Thanks,

  - Michael

  Posted 22 years ago #

• mstielau Member

  Jim,

  I sent an e-mail to the web hosting company and explained the problem with their server, and this is the reply I just received...

  <i>This problem is only with the program that you are using.

  Any other software that attempts to pull the file in question, .bash_history in your root directory, reports the correct size of 860 bytes.

  Unfortunaly since all other programs are reporting the proper file size there is not anything on the server that we can correct.</i>

  One other thing - I noticed that when I select the file .bash_history in the Fetch window, and select Get Info from the contextual menu, it correctly reports the file size as 860 bytes. Where is that information coming from?

  - Michael

  Posted 22 years ago #

• Jim Matthews Administrator

  Unfortunaly since all other programs are reporting the proper file size there is not anything on the server that we can correct.

  :mad:

  This is nonsense -- the SIZE command is malfunctioning, and that can only be corrected on the server. I would be happy to trade email with this server administrator.

  Fetch gets the correct size from the file list command (LIST). But it prefers the information from the SIZE command, since in general that command is more accurate -- its whole purpose is to return the file size.

  Jim Matthews
  Fetch Softworks

  [This message has been edited by JimMatthews (edited 11-09-2001).]

  Posted 22 years ago #

• mstielau Member

  I thought it sounded fishy too.

  Thanks for your offer to communicate with the hosting service on this issue. I have e-mailed the relevant contact information to you.

  - Michael

  Posted 22 years ago #

• mstielau Member

  Jim,

  I solved this problem once and for all by dumping this particular web hosting service in favor of a competent one. The nonsensical answers we got from them in trying to resolve this issue was representative of the "service" they were providing. (If anyone wants to know their identity, please e-mail me privately.)

  Thanks again for your help,

  - Michael

  Posted 22 years ago #