TiTaNiuM sAMuRai Posted July 11, 2002 Share Posted July 11, 2002 Rarely can I purge or Revert to Saved without the program crashing. Was this irregular behavior in v8 not tracked down? Is it still on the list of unresolved issues? I don't know, you see, since no 'internal' bug dbase is published... Quote Link to comment
PeterT Posted July 11, 2002 Share Posted July 11, 2002 I have noted as well that when I revert to saved in VW 9.5.2 on Mac OS 10.1.5 VectorWorks will crash, but only on files that are saved on our server and opened across the network. Files saved on the same machine as the alpplication revert to saved just fine. Work arounds for the crash problem are: 1. Instead of revert to saved, just close the file without saving changes, then re-open it again (does the same thing as revert). 2. Use multiple undo to back track to the last point you saved. I have identified the crash when reverting to a file on the server to Nemetschek telephone tech support and they replicated the problem on their machines too. I was told it would be added to the bug list. Quote Link to comment
Guest Posted July 11, 2002 Share Posted July 11, 2002 Asside from the OS 10's Unexpected error has occured ... on other operating systems, do you get an error message? I can't think of any time that I've had it happen to me. If there is a specific file/files that you are having this problem with, you should submit it to bug submit to see what they find. Quote Link to comment
ionw Posted July 12, 2002 Share Posted July 12, 2002 We have this problem at our office as well. One thing I have noticed is that the person that complains the most is one of our most prolific users of workgroup references, though it has happened to me as well in files that do not have WGRs in them. and no, no special message just "Vectoworks has unexpectedly quit..." Quote Link to comment
joe newell's ghost Posted July 12, 2002 Share Posted July 12, 2002 And this is a bit off topic but is it just laziness that prompted our noble programmers to come up with that delightfully un-informative and redundant message "Vectorworks has unexpectedly quit" as a catch all for every crash ever experienced by a Vectorworks user for any reason whatsoever? Just curious Quote Link to comment
ccroft Posted July 13, 2002 Share Posted July 13, 2002 "Vectorworks has unexpectedly quit" is a message from the operating system, not v-works. The OS doesn't know why. Other such messages include "The Finder has unexpectedly quit" or "Error Type xyz" and they're all pretty useless as a trouble shooting tool. I use revert a fair bit and have never had a crash. Maybe it is a network thing as was mentioned earlier. I run v-works on one machine. Quote Link to comment
TiTaNiuM sAMuRai Posted July 13, 2002 Author Share Posted July 13, 2002 On OS9.x, it's tough to tell if this happens because VW crashes for so many other reasons. We don't save on local machines; all our work is done over the network, saving to a file server. Let it be noted that in our case, I'm a OSX client saving to a OS9.1 machine (with OS9 AppleShare IP, therefore). Quote Link to comment
Matthew Giampapa Posted July 15, 2002 Share Posted July 15, 2002 "VectorWorks has unexpectedly quit" is a message that you will see if the problem is something we didn't anticipate, or is so severe that the OS kills VectorWorks before anything else happens. So it's sort of a catch all. If we either knew what the error was, or had time to display a relevant error message we would. In a large number of cases, you just can't issue a good error because the OS won't let you go into the error handling code. The only recourse for this is to use a debug version of the program so you can actually see where in the code the error occurred, put in a break point, and then reproduce the error to see the state of the program. I do know for a fact that at least a few bugs dealing with revert to saved and MacOS X in the bug list. These should be fixed for the next major release. If there are other situations where this happens we would like to know... TS, were you just seeing this in v8? or could you reproduce it in v9 as well? Matthew GiampapaNNA Technical Support Quote Link to comment
TiTaNiuM sAMuRai Posted July 16, 2002 Author Share Posted July 16, 2002 Matt: It was in 8.5.2 (under OS9) and in 9.5.1 (under OSX). Maybe it was just the type of file work I was doing, but I noticed far less crashing with 950b5 and b7. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.