Jump to content

Frequent Crashes


Recommended Posts

Wizards,

VW has been crashing a lot on me.

It occurs only on one file, or its' offspring that I created by 'saving a copy as'.

It does not appear to be associated with any particular action on my part. For a while it appeared to be the result of my rather abrupt zooming in and out. Then I thought it might be the 'rectangle' tool. But not so - I tried repeating my actions right before the crash in another file and no crash occurred.

This file does have a fair amount of stuff imported in the form of .dwg from other sources, which distinguishes it from the other files that appear to be more stable, but they too have some. The file is 9.8MB, which seems tiny as far as these things go.

I am using VW 2008 on a MacBook, OS10.5.7. There is tons of RAM and hard-drive space available.

Any ideas on possible causes, or work-arounds.

Thanks tons,

Phillip

Link to comment

Pat,

I must say that I am not sure when I upgraded to 10.5.7. (I just checked the 'Installer Log', and it looks like 10.5.7 was installed on May 21) The crashes started more recently. . .say 2 or 3 days ago at the most. VW crashed twice maybe 30 minutes apart. At that point I reset VW to backup every minute. The OS is in general very stable.

So far it has only crashed on one particular file (of course the biggest project I have going on, and with the tightest schedule, and so on and so forth) and a 'saved copy' of that same file.

After writing the original post I did work for about an hour on the file, with no crashes. I did not notice any abnormal behavior in the way VW performed.

Can you uninstall an OS update? Sounds unlikely, especially for someone of my technical abilities (none).

I think at this point I'll try to work with fewer applications open and keep more accurate track of when VW crashes.

Thanks,

Phillip

Link to comment
Guest Lyndsey

I agree with islandmon, look at the Console logs. In the Finder, navigate to /Applications/Utilities and launch the Console application.

There are two sources of useful information:

1 - The Crash Log as islandmon suggested. That can be found under the CrashReporter group (in the LOG FILES group).

2 - The Console Messages found in the LOG DATABASE QUERIES. Often there are some hints of various problems occuring.

Link to comment

Learning more about my computer than I ever wanted. . .or thought possible.

What is WGR?

OS 0.5.7 was installed on 5/14/09.

The first crash was 3/09/09, so I am somewhat dubious about that being the cause.

Following the advice I looked in the Crash Reporter, and found this:

Jun 2 18:16:47 Macintosh ReportCrash[556]: Formulating crash report for process VectorWorks[168]

Jun 2 18:16:51 Macintosh ReportCrash[556]: Saved crashreport to /Users/phillipcollins/Library/Logs/CrashReporter/VectorWorks_2009-06-02-181636_Macintosh.crash using uid: 501 gid: 20, euid: 501 egid: 20

Jun 2 18:16:48 Macintosh com.apple.launchd[63] ([0x0-0x1f01f].net.nemetschek.vectorworks[168]): Exited abnormally: Bus error

Below is a small (very) portion of the Crash Report - does this possibly mean anything to anybody? Each crash has it's own report, so when I get some time I will go through them to see if there are any similarities.

Process: VectorWorks [168]

Path: /Applications/VectorWorks 2008/VectorWorks 2008.app/Contents/MacOS/VectorWorks

Identifier: net.nemetschek.vectorworks

Version: 13.0.1 (88670) (???)

Code Type: X86 (Native)

Parent Process: launchd [63]

Date/Time: 2009-06-02 18:16:36.915 -0700

OS Version: Mac OS X 10.5.7 (9J61)

Report Version: 6

Anonymous UUID: FA475B6C-9704-43E8-A486-161B81EDEF36

Exception Type: EXC_BAD_ACCESS (SIGBUS)

Exception Codes: KERN_PROTECTION_FAILURE at 0x000000000000000c

Crashed Thread: 0

Thread 0 Crashed:

0 net.nemetschek.vectorworks 0x004d4fff start + 5056295

1 net.nemetschek.vectorworks 0x004cbdce start + 5018870

2 net.nemetschek.vectorworks 0x004cbf5d start + 5019269

3 net.nemetschek.vectorworks 0x004d3568 start + 5049488

4 net.nemetschek.vectorworks 0x004d38d4 start + 5050364

5 net.nemetschek.vectorworks 0x002ae70f start + 2801207

6 net.nemetschek.vectorworks 0x001a5455 start + 1715069

7 net.nemetschek.vectorworks 0x00050b08 start + 320048

8 net.nemetschek.vectorworks 0x000baf95 start + 755389

9 net.nemetschek.vectorworks 0x000ca154 start + 817276

10 net.nemetschek.vectorworks 0x0005b2b9 start + 362977

11 net.nemetschek.vectorworks 0x000b44d2 start + 728058

12 net.nemetschek.vectorworks 0x000b3d7e start + 726182

13 net.nemetschek.vectorworks 0x0005ad3f start + 361575

14 net.nemetschek.vectorworks 0x000029da start + 258

15 net.nemetschek.vectorworks 0x00002901 start + 41

Thanks for all the suggestions.

Phillip

Link to comment

I'm not so sure if this applies, but I've read in another thread that reducing the number of undos in Vw preferences to 10 or less will improve performance.

Another thing that comes to mind is using the "Update Plug-in Objects" under Tools > Utilities (in case the file was made with an earlier version).

Edited by Bob-H
Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...