joelhufford Posted January 11, 2015 Share Posted January 11, 2015 I'm wondering if anyone else is experiencing VW2015 crashes after attempting to change the color (fill or stroke, doesn't seem to matter) of an object in a drawing? I had not suffered from this before the SP2 update, but it seems now that every drawing I work on is prone to this behavior. When I upgraded from 14 to 15 I did not do a fresh install so I thought that might be the issue, but after a clean install yesterday I've just had another drawing crash! I'm confused because 2015 has been so stable up to this point. I suppose it's worth noting that in the last 6 weeks I've also updated my computer to Mavericks, but according to Nemetschek, VW2015 and Mavericks are supposed to place nice together. Computer info and crash log for crashed thread pasted below: Model: MacBookPro9,1, Intel Core i7, 2.3 GHz Quad Core Graphics: NVIDIA GeForce GT 650M, 512 MB + Intel HD Graphics 4000, Built-In Memory: 16 GB, DDR3 1600 MHz Mac OS X 10.9.5 Vectorworks 2015 SP2 *** CRASH LOG *** Process: Vectorworks [7211] Path: /Applications/Vectorworks 2015/Vectorworks 2015.app/Contents/MacOS/Vectorworks Identifier: net.nemetschek.vectorworks Version: 20.0.2 [240846] (20.0.2) Code Type: X86-64 (Native) Parent Process: launchd [337] Responsible: Vectorworks [7211] User ID: 503 Date/Time: 2015-01-10 21:49:53.879 -0700 OS Version: Mac OS X 10.9.5 (13F34) Report Version: 11 Anonymous UUID: 1E3D402E-C419-99ED-C3F1-324EB50606B1 Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: EXC_I386_GPFLT Application Specific Information: objc_msgSend() selector name: collectionView:cellForIndex: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libobjc.A.dylib 0x00007fff85540097 objc_msgSend + 23 1 net.nemetschek.vectorworks.ColorPalettes 0x00000001249bcb20 0x124994000 + 166688 2 com.apple.Foundation 0x00007fff83b7c93e __NSIndexSetEnumerate + 1316 3 net.nemetschek.vectorworks.ColorPalettes 0x00000001249bcac5 0x124994000 + 166597 4 net.nemetschek.vectorworks.ColorPalettes 0x00000001249bce43 0x124994000 + 167491 5 com.apple.CoreFoundation 0x00007fff86199e0c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12 6 com.apple.CoreFoundation 0x00007fff8608d82d _CFXNotificationPost + 2893 7 com.apple.Foundation 0x00007fff83b25e4a -[NSNotificationCenter postNotificationName:object:userInfo:] + 68 8 com.apple.AppKit 0x00007fff86d4f935 -[NSView _postBoundsChangeNotification] + 179 9 com.apple.AppKit 0x00007fff86d4f748 -[NSView translateOriginToPoint:] + 294 10 com.apple.AppKit 0x00007fff86bf7270 -[NSClipView _immediateScrollToPoint:] + 4292 11 com.apple.AppKit 0x00007fff86bf616a -[NSClipView scrollToPoint:] + 237 12 com.apple.AppKit 0x00007fff86d4ebae -[NSScrollView scrollClipView:toPoint:] + 203 13 com.apple.AppKit 0x00007fff86bfadc9 -[NSClipView _scrollTo:animateScroll:flashScrollerKnobs:] + 1688 14 com.apple.AppKit 0x00007fff86d249c8 -[NSClipView _scrollTo:animate:] + 28 15 com.apple.AppKit 0x00007fff86eaff5f __68-[NSScrollingBehaviorLegacy _scrollView:snabRubberBandWithVelocity:]_block_invoke_2 + 831 16 com.apple.AppKit 0x00007fff86eaf205 ____NSPeriodicInvokerScheduled_block_invoke + 58 17 libdispatch.dylib 0x00007fff8bdae1bb _dispatch_call_block_and_release + 12 18 libdispatch.dylib 0x00007fff8bdab28d _dispatch_client_callout + 8 19 libdispatch.dylib 0x00007fff8bdb2ef0 _dispatch_main_queue_callback_4CF + 333 20 com.apple.CoreFoundation 0x00007fff861324f9 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9 21 com.apple.CoreFoundation 0x00007fff860ed714 __CFRunLoopRun + 1636 22 com.apple.CoreFoundation 0x00007fff860ece75 CFRunLoopRunSpecific + 309 23 com.apple.HIToolbox 0x00007fff8b4b5a0d RunCurrentEventLoopInMode + 226 24 com.apple.HIToolbox 0x00007fff8b4b57b7 ReceiveNextEventCommon + 479 25 com.apple.HIToolbox 0x00007fff8b4b55bc _BlockUntilNextEventMatchingListInModeWithFilter + 65 26 com.apple.AppKit 0x00007fff86b9124e _DPSNextEvent + 1434 27 com.apple.AppKit 0x00007fff86b9089b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122 28 net.nemetschek.vectorworks 0x0000000104396b01 0x104225000 + 1514241 29 com.apple.AppKit 0x00007fff86b8499c -[NSApplication run] + 553 30 com.apple.AppKit 0x00007fff86b6f783 NSApplicationMain + 940 31 net.nemetschek.vectorworks 0x0000000104227784 start + 52 Quote Link to comment
Vectorworks, Inc Employee PVA - Admin Posted January 12, 2015 Vectorworks, Inc Employee Share Posted January 12, 2015 I am unable to replicate this here. Could you post any file where the issue happened, mark the object you changed the color on, note what color you tried to change it from and to so that I can have a closer look? Quote Link to comment
joelhufford Posted January 20, 2015 Author Share Posted January 20, 2015 Hi Jim, Thank you for once again for being so quick to respond in this thread! So awesome! I'm afraid the crashing is very sporadic and all of the documents I lost to a crash were brand new documents I had not saved when they crashed. I'd love to send you a crashing document, but I can't seem to replicate this! I was just reading the other thread about the eyedropper causing some problems and am wondering if somehow these two problems could be related? It does look like the last 8 crashes that I've experienced using VW 2015 SP2 have involved a call to net.nemetschek.vectorworks.ColorPalettes and then crashed with the same call to libobjc.A.dylib method: objc_msgSend + 23. This also shows up in the application specific portion of most, but not all crash logs: Application Specific Information: objc_msgSend() selector name: collectionView:cellForIndex: Performing @selector(menuItemSelector:) from sender NNAMenuItem 0x6100002d0680 Not sure if that's helpful at all. As soon as I encounter a problematic file, I'll be happy to send it your way. Thanks, Joel Quote Link to comment
joelhufford Posted January 20, 2015 Author Share Posted January 20, 2015 Lo and behold! seems i am able to reproduce the crash consistently with the attached file. It appears to happen when selecting a color from the color palette while the palette is scrolling, but before the scrolling animation has completed. Also I just opened a new file and was able to reproduce the same behavior. I suppose the solution in the mean time is to just slow down when picking colors! Please let me know if you're able to reproduce this, or if this is a viable excuse I can use to tell my boss it's time to upgrade to one of them shiny new MacPros! Thanks, Joel Dropbox to Crashing VW2015 File Quote Link to comment
michaelk Posted January 20, 2015 Share Posted January 20, 2015 I can't make it crash. In fact, I can't get the color picker scroll slow enough to pick something while it's still scrolling. There's no lag in the scrolling animation. We have almost identical computers. I have the 2.6 GHz i7. Same year. I'm also running 10.8.5. strange. mk Quote Link to comment
joelhufford Posted January 20, 2015 Author Share Posted January 20, 2015 Hi Michael, It's not that the animation is lagging, the application just crashes when I click on the color palette while it's still scrolling. Check out the video below. the first time I select a color after scrolling has finished. The second time during a scroll and it crashes. https://www.dropbox.com/s/lhh4s62rbjrenu9/vw2015%20crash.mov?dl=0 Quote Link to comment
MC4 Posted January 20, 2015 Share Posted January 20, 2015 I have a similar problem . VW 2015 crashes when selecting a texture for an object Quote Link to comment
Vectorworks, Inc Employee PVA - Admin Posted January 20, 2015 Vectorworks, Inc Employee Share Posted January 20, 2015 Make sure to get in touch with tech support directly about those, unable to replicate the crashes here on 2015 sp2. Quote Link to comment
bcd Posted January 20, 2015 Share Posted January 20, 2015 Sounds familiar here too - it's rare but I've seen it. Quote Link to comment
michaelk Posted January 20, 2015 Share Posted January 20, 2015 Joel Wow. When I do exactly the same thing on an almost identical machine running the same OS, I can't get it to crash. In general, I've found that 2015 crashes so rarely that I've gotten out of the habit of hitting command S before every viewport update or every section or every render. I'm seeing a crash about once every two weeks. There's been some chatter here about other apps that are incompatible with VW. Have you tried running VW in a test user account w/ no system extensions and nothing else running? mk Quote Link to comment
Vectorworks, Inc Employee PVA - Admin Posted January 20, 2015 Vectorworks, Inc Employee Share Posted January 20, 2015 (edited) Thats always worth a shot: http://kbase.vectorworks.net/questions/805/Creating+a+New+User+Account+%28Mac+OS+X%29 However if a shiny new Mac Pro is on the line... Edited January 20, 2015 by JimW Quote Link to comment
michaelk Posted January 20, 2015 Share Posted January 20, 2015 Jim's right. I take it back. Get a Mac Pro. mk Quote Link to comment
joelhufford Posted January 21, 2015 Author Share Posted January 21, 2015 Haven't tested the new user account... I'll give it a go after all the Super Bowl madness subsides! Thanks guys, Joel Quote Link to comment
joelhufford Posted January 23, 2015 Author Share Posted January 23, 2015 Ok, just sat down and tested this with a new user account... same results! Any other thoughts? I've already done a fresh install once... https://www.dropbox.com/s/dsmfljf1p77khnt/new%20account%20crash.mov?dl=0 Quote Link to comment
simon.norman Posted March 23, 2017 Share Posted March 23, 2017 Has anyone had any luck solving this? Our users are having loads of frequent crashes because of this problem - they go to change a colour, select a colour from the palette, and the system crashes. Quote Link to comment
Vectorworks, Inc Employee PVA - Admin Posted March 23, 2017 Vectorworks, Inc Employee Share Posted March 23, 2017 13 minutes ago, simon.norman said: Has anyone had any luck solving this? Our users are having loads of frequent crashes because of this problem - they go to change a colour, select a colour from the palette, and the system crashes. Are you using Vectorworks 2015? Which service pack? What operating system are you using? Are all of these users on the same hardware/OS? Quote Link to comment
simon.norman Posted March 27, 2017 Share Posted March 27, 2017 Vectorworks 2016, Windows 10, everyone on the same OS and hardware, build 278524 (original 2016 version). Quote Link to comment
simon.norman Posted March 27, 2017 Share Posted March 27, 2017 (edited) Varies slightly in terms of service pack - different machines have different versions. One I just checked that it was crashing on was 2016, build 278524. Edited March 27, 2017 by simon.norman Quote Link to comment
Vectorworks, Inc Employee PVA - Admin Posted March 27, 2017 Vectorworks, Inc Employee Share Posted March 27, 2017 Install 2016 SP6 on one of these machines, and tell me if you are able to replicate the issue in a new blank file. http://www.vectorworks.net/support/downloads/product-updates?version=2016 Quote Link to comment
simon.norman Posted April 12, 2017 Share Posted April 12, 2017 OK, we've updated all the machines to 2016 SP6. There was a crash yesterday - I have attached the crash logs (two DMP files were created, which I've zipped and uploaded). The crash happened when the user changed the colour of a polygon. Vectorworks2016_exe.15068.zip Vectorworks2016.exe(1).15068.zip Quote Link to comment
Vectorworks, Inc Employee PVA - Admin Posted April 12, 2017 Vectorworks, Inc Employee Share Posted April 12, 2017 This crash occurred in a new file? Or an existing document from another version/SP? Quote Link to comment
simon.norman Posted April 18, 2017 Share Posted April 18, 2017 It definitely wasn't a new file - but not sure if it had been created in another version / SP. Does that matter? If that's the case, is there no way to fix this? Quote Link to comment
Vectorworks, Inc Employee PVA - Admin Posted April 18, 2017 Vectorworks, Inc Employee Share Posted April 18, 2017 In a new blank files, does it also crash now? If you open that same file where the crash did occur, and it still crashes, make sure to get that file to technical support directly and they can take a look. Quote Link to comment
simon.norman Posted April 19, 2017 Share Posted April 19, 2017 It doesn't crash (or not that I can find or have heard) with a new blank file - but I wouldn't call this conclusive. How can I get that file to technical support? Quote Link to comment
Vectorworks, Inc Employee PVA - Admin Posted April 19, 2017 Vectorworks, Inc Employee Share Posted April 19, 2017 Apologies, no it wasn't meant to be conclusive, it just separates the issue out from being a problem with the tool or you installation, as opposed to a file related problem. Something is still broken it's just a matter of tracking it down. Tech@vectorworks.net is the most direct method, if the file is too large to email, then mention that in your email description of the issue and they can send you a link to upload it directly. I recommend you reference this thread in the email so that they can see the history and don't need to have you repeat tests. 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.