SUpro 7 on OSX 10.5.6 locks up entire UI for all apps

tim

... and requires a reboot.

There seems to be a faint possibility of some interaction with Time Machine, possibly some file locking or whatever. This is based on the lockups occurring around the time of a backup, but not apparently exactly on time.

I've had total lockups several times over the last couple of weeks as I work on SU designing a moderately large model. The console log shows a large number of

27/01/09 27 Jan 6;53;17 PM SketchUp[1696] SketchUp(1696,0xa0097720) malloc; *** error for object 0xa063a6d8; Non-aligned pointer being freed
*** set a breakpoint in malloc_error_break to debug

and

27/01/09 27 Jan 6;53;17 PM [0x0-0xe60e6].com.google.sketchuppro7[1696] SketchUp(1696,0xa0097720) malloc; *** error for object 0xa063a6d8; Non-aligned pointer being freed

and

27/01/09 27 Jan 6;53;17 PM [0x0-0xe60e6].com.google.sketchuppro7[1696] *** set a breakpoint in malloc_error_break to debug

type reports.

Even if these aren't actually the root cause of the problem it is pretty poor practise to have such bad alloc/free behaviour.

I also see plenty of

27/01/09 27 Jan 6;55;36 PM SketchUp[1696] _NSShapePlainWindow; error setting window shape (1000)

and from the windowserver log

Jan 27 18;55;36  [88] kCGErrorFailure; CGXShapeWindow; Cannot chnage backing store size
Jan 27 18;55;36  [88] kCGErrorNoneAvailable; allocTaskVM; vm_map (3; (os/kern) no space available) requested 0x5f000 bytes anywhere
Jan 27 18;55;36  [88] kCGErrorNoneAvailable; CGXBackingStoreResize ; Cannot create data backing store
Jan 27 18;55;36  [88] kCGErrorFailure; CGXShapeWindow; Cannot chnage backing store size
Jan 27 18;55;36  [88] compressData; destinatinon buffer size 0 too small for y index (3852)

Jan 27 18;55;37  [88] compressData; destinatinon buffer size 0 too small for y index (3852)

Jan 27 18;55;37  [88] compressData; destinatinon buffer size 0 too small for y index (3852)

errors just before the time of the lockup.

Anybody else having this sort of problem? Any suggestions ?

Edson

i am running Su7, 10.5.6 and Time Machine with none of the problems described.

bertb

Me too, no problems whatsoever,
at least untill now

tim

Glad you're not having any problems!

If you look in your logs (start the Console {in Appliations:Utilities}) and scan the 'all messages' log (under 'LOG DATABASE QUERIES'), do you see any messages about SU failing to free objects? In the 'windowserver.log' (under 'LOG FILES')do you see any complaints at all?

What machines are you using? Mine is a 2.4GHz core 2 duo iMac with 4Gb ram and an external 20" display, fully up to date in software.

Edson

i could not find anything like that.

Macbook Pro 2.4ghz core 2 duo, 4mb ram, external 20"apple cinema display.

tim

Well it's happened several more times now; definitely some variety of memory leak eventually causing the core graphics systems to lock up. That really, really, shouldn't be possible. Ah well, I reported it to google and apple and we'll see if anything every happens as a result.

I've even done hardware tests and reseated/swapped the memory to no avail.

It's actually scary running with the Console open on the 'All Messages' view - the number of problems in all sorts of programs that get reported is horrififc.

Edson

perhaps you should get apple's technical assistance. your problem seems to be beyond what a regular user can solve by himself.

Nicoloco

Having exactly the same problem on three different machines in the office. System locks up and requires a hard reboot after about 10 minutes. I have filed a bug report with Sketchup and have started a thread on the Goodle Groups Sketchup Pro board.

http://groups.google.com/group/Sketchup-Pro/browse_thread/thread/8f43b383f71ac697/7cb353f62aae219a?hl=en#7cb353f62aae219a

I have discounted Time Machine as we are not using it. Also, my Mac Pro doesn't have an Airport, so I don't think its that. Also, it seems independent of video cards as people with NVidia and ATI Radeon cards are experiencing the same problems.

Interestingly, it is only happening on one particular job and not on another. Both models had been created in SU6 from DWGs and were pretty complex. They have both been purged and checked/fixed. I will try at lunchtime with a completely new SU7 model and see if I can crash it; which should discount the legacy artifact theory.

Other things I have noticed:

Turning off 'Hardware Acceleration' seems to make it stable (no crashes in 8 hours of (very slow) use)
Turning off 'Auto-Save' seemed to be working, but then experienced an application crash.

Seriously though, I need to get back to doing my job of designing things, so if anyone finds a fix that would be great!

Nick

Gaieus

Hi Nick and welcome (although would be nicer if you didn't have to come here with this bad news).

I'm personally on PC so won't be much help however Catamountain over the Help Groups is quite knowledgeable at these fields as I've noticed.

Hopefully someone with more Mac experience will chime in.

tim

Nico - yes, I ran with TM turned off just in case and it made no difference. One interesting thing I have noticed is that the alloc/free error logged is always for the same address no matter what apps I am runnig, whether I've rebooted, got several SU models open or whatever.
I too have done various purges with no improvement. I haven't used any extension ruby apps either.

As an experiment to see if it was perhaps some apple kernel library change from recent updates I've been using SU6 for the last couple of days with none of the related problems.

Nicoloco

Tim,

Agree with that. Half of our office are still using Sketchup 6 Pro and none of them (out of 10) have reported a crash whilst it is happening to all (6 in total) of the Sketchup 7 Pro users. Everyone is running OSX 10.5.6. Happening to a variety of machines...Mac Pro, Intel iMacs and MacBook Pro. Can't see a common link in terms of video cards as they are a mixture of NVidia and Radeon cards. Turning off 'Hardware Acceleration' fixes the problem in all cases, but makes modelling nearly impossible.

Other programmes that are usually running at the same time:

Safari/Firefox, Mail, AddressBook, CS3, iTunes, Vectorworks 2008, Office.

However, I have started up the computer, disabled all of the startup items, booted it without extensions, not connected to the server and ONLY run Sketchup Pro 7 and the same thing happens.

How did you get the information about where the memory allocation problem was? I will do that next time (at lunchtime) and see if it matches yours.

Nick

tim

Nick, I've been running the Console application to keep an eye on the errors being reported as the system runs. It's quite.... alarming. So many apps reporting failed this, can't do that and the kernel won't do the other.

The Console has a list on the left that shows all the logs it maintains. The two that seem important here are the 'All Messages' log which has been listing a lot of alloc related messages, and the 'WindowServer.log' (expand the 'LOG FILES' entry by clicking on the triangle) which was showing the backing store type messages.

On the plus side I just received a message from the google-guys suggesting a full de-install and re-install since they suspect some component was not installed correctly. They suggest :-

@unknownuser said:

Uninstall Google SketchUp Pro 7 by visiting the following Google
SketchUp Help Center article:

http://sketchup.google.com/support/bin/answer.py?answer=36209

After uninstalling, we suggest repairing disk permissions:

a. Restart your computer.
b. Open a Finder window.
c. Click "Applications."
d. Click "Utilities."
e. Double-click "Disk Utility."
f. Select your hard drive.
g. Select the "First Aid" tab.
h. Click "Repair Disk Permissions."
i. After the permissions are repaired, exit Disk Utility.
j. Please repeat steps "a" through "i" once more.

Log in to your computer with a user account that has administrative
privileges.

Please visit
http://sketchup.google.com/support/bin/answer.py?answer=115548 and
download the Google SketchUp Pro 7 install file.

When the download completes, double-click on the install file and
follow the on-screen instructions.

Please launch Google SketchUp at least once while still logged into the
administrative user account.

It certainly seems to have massively reduced the alloc related messages so I'll see how it goes.

Nicoloco

Tim,

Thanks. Have made a clean installation of Sketchup 7 Pro as per the Google instructions. Had a look in the console and there are still lots (about 4000 in three seconds...) of the following messages.

09/02/2009 12;11;48 [0x0-0x110110].com.google.sketchuppro7[761] *** set a breakpoint in malloc_error_break to debug

and

09/02/2009 12;11;48 [0x0-0x110110].com.google.sketchuppro7[761] SketchUp(761,0xa077d720) malloc; *** error for object 0xa06eb6d8; Non-aligned pointer being freed

Have turned off 'Fast Feedback' and left 'Hardware Acceleration' on and this has eliminated the crashing (none yet today) without too much of a performance hit. It doesn't seem to have any effect on the error messages.

Nick

tim

Oh well, nice idea google-guys. I just had a repeat of the exact same crash as before. Let's see what the next suggestion is like!

bjanzen

Tim -

Those console msgs have been there for a couple of versions, and yes, it'd be nice if someone cleaned them up. Do you get the Apple crash log showing up? If you do, don't send to Apple - send it to us by copying the text in it and sending it to us in an e-mail so we can troubleshoot. I'll poke through this and other things and see if we know anything more. Thanks.

Barry

tim

Hi Barry -
no, there is no crash report as such, just the log messages in the windowserver.log and then total UI death. It may be of interest that iTunes keeps on playing, and don't forget that I can log in from one of my other macs and poke around. That might allow some sort of remote debugging experiments? Let me know. My time is my own for a week or so, so I can spend some if it working on this with you if you have tests for me to try.

It might sound callous but I'm glad someone else with different equipment is having similar crashes. At least that offers some more chance of reproducibility. I used to hate intermittent errors when I was managing s/w development...

TriciaS

A few more questions on this one.

Nicoloco - are you still not crashing with Fast Feedback off? If so, that is a really important clue. If you turn on Fast Feedback, can you recreate the issue with all models or just certain ones? It sounds like you were thinking it might be model related...

Tim - does turning off Fast Feedback in Preferences > OpenGL seem to fix your lock up as well?

Fast Feedback speeds up the drawing actions in your model (vs things like the speed at which you can orbit around) and only kicks in when performance degrades below a certain threshold. So Fast Feedback will only kick in when working on larger models. If you both are only seeing this issue with more complex models when Fast Feedback is enabled, that might be a further clue.

Also, we are wondering if you see a pattern in how many document windows you have open at the time of the crash. Or whether it seems to happen only with certain actions - e.g. only when adding geometry, or when selecting things etc...

Sorry for all the questions. We really appreciate your willingness to help us try to get to the bottom of this one.

Tricia

tim

@unknownuser said:

I'll try it and see.

@unknownuser said:

Also, we are wondering if you see a pattern in how many document windows you have open at the time of the crash. Or whether it seems to happen only with certain actions - e.g. only when adding geometry, or when selecting things etc...

I very rarely have more than 2 document windows open - so rarely I can't remember doing it. I do tend to have most of the tool windows open (layers, outliner, styles, components etc) most of the time. I can't discern any pattern of actions involved.

My model is not particularly complex
30,000 edges
13,000 faces
622 component instances
2 groups
3 images
235 component definitions
10 layers
47 materials
1 style
everything else 0

Don't worry about asking questions; I'll only get worried when you d

I'll try it and see.

@unknownuser said:

Also, we are wondering if you see a pattern in how many document windows you have open at the time of the crash. Or whether it seems to happen only with certain actions - e.g. only when adding geometry, or when selecting things etc...

I very rarely have more than 2 document windows open - so rarely I can't remember doing it. I do tend to have most of the tool windows open (layers, outliner, styles, components etc) most of the time. I can't discern any pattern of actions involved.

My model is not particularly complex
30,000 edges
13,000 faces
622 component instances
2 groups
3 images
235 component definitions
10 layers
47 materials
1 style
everything else 0

Don't worry about asking questions; I'll only get worried when you don't....

tim

@tim said:

@tricias said:

Tim - does turning off Fast Feedback in Preferences > OpenGL seem to fix your lock up as well?

I'll try it and see.

Sigh. No improvement at all. Exactly the same errors logged, exactly the same lock-up.

bjanzen

Nicoloco & Tim -

In Finder, type Command-Shift-g and type ~/Library/Logs/CrashReporter/ This directory contains all the crashes on your machine. You can send us a typical SketchUp crash.

Tim, yours messages point to WindowServer unable to create swap space. Is your hard drive nearly full, or are you running a lot of screens in Spaces? You posted that WindowServer threw errors - is WindowServer still running? If you remote'd in, do a "ps aux | grep Window" command is WindowServer there? You can also run "top", type "o" (to sort on) then "cpu" to sort on cpu usage. WindowServer will always be near the top. If it didn't crash, what's the memory usage (my machine, just typical usage, is 130 MB real memory, 500 MB virtual memory). If this is crashing or messed up, we can contact Apple and work with them to find out what's going on.

Please do or continue to send data (crash logs, system profiles, etc..) to

http://sketchup.google.com/support/bin/request.py

I'm still of the belief that your situations are unique - we have lots of users in 10.5.6 with zero problems, so we'll try to determine what's going on for you.

b