Back to Rhino aggain!!
-
@andrews said:
I was able to correlate the crash from the provided data. If we're talking about the same one, it came from an IP address in Bulgaria on 2014-03-25 at 11:38:06. The name of the Windows login account is "cadmaster". The BugSplat ID of the report is 10592. The rest of the message is in reference to this specific BugSplat.
That BugSplat shows that SketchUp crashed while executing a Ruby script. It is possible that there's a bug in the Ruby API that allowed a well behaved script to fail. More likely though, the Ruby script that was executing did something wrong and killed SketchUp as a result.
Looking at the crash data the crash happen when a plugin tries to get the name of a style. I'm not able to figure out which. I can't see the plugin doing anything wrong here, the crash appear to be our fault. But if we can figure out which plugin it is we could assist in a workaround until we can fix the crash on our end.
However, I'm not sure how to reproduce.@andrews said:
Normally it is very difficult for us to figure out which plugin is misbehaving when it dies. I was able to see that a plugin called "jf_trim_and_keep.rb" was executed before the crash, but I think it completed successfully. I don't think there's a clear indication of the problem-causing plugin in the undo log.
Yea, I'm also not sure which plugin triggers this. I'd start looking at any plugins you can think of that deals with the model styles in any way.
@andrews said:
As I said, it's normally very difficult to figure out which plugin crashed from BugSplat data. However, in this case, two big clues stand out which point to the likely cause. First, the list of currently loaded libraries contains Thea4SU_core.so. Second, the call stack shows that there is an active thread on the CPU working inside the Thea4SU_core library at the time of the crash.
I'm guessing Thea wasn't necessarily being actively used or that fact would have been mentioned. Regardless, it actually might not matter. I believe ThomThom has documented elsewhere that Thea is known to cause problems when it's run in the background but isn't being used. If my recollection of that is correct, it would seem that the workaround to this specific crash is to disable Thea when you're not rendering, then save everything and quit before re-enabling Thea when you want to render.
[/quote]
Render engines in general has historically been prone to destabilizing things, mostly due to their heavy reliance of observers. Again, the real cause is in our code, observers a volatile items in the current API and we need to improve them. -
Yes, it was our office computer. Sorry, but we removed SketchUp - so, I can't collaborate further. Sure, SketchUp is pretty stable as a vanilla and almost useless for us without a bunch of plugins! It was my first 3d program and I can't stop going back to it
-
Don't recall if Thea for SU had actually crashed SU for me (but I am using a old SU8), still there been reports (at Thea forums) that v-ray for SU and Thea for SU together may result a crash (SU 2013 & OS X). If just Thea for SU where used, everything where fine. Tomasz probably do know better, if there further details on this.
-
@notareal said:
Don't recall if Thea for SU had actually crashed SU for me (but I am using a old SU8), still there been reports (at Thea forums) that v-ray for SU and Thea for SU together may result a crash (SU 2013 & OS X). If just Thea for SU where used, everything where fine. Tomasz probably do know better, if there further details on this.
Multiple render engines together has historically been known to increase chance of crashes - usually due to competing observers working at the same time affecting the model.
-
Dear All,
I've been using Sketchup for 7 years and have some tips to share about crashed:
1)Actually Modelling program like CAD, MAX, Rhino and Sketchup always have a limitation of precision. You will never be able to draw an ant standing on earth and flying around the sun. It's computing limitation.
So, sometime my sketchup crashed when I tried to import(paste) a model with very small details (1/10 millimeter) into an large scale urban masterplan (20 kilometer).
2)And you should clean your sketchup file to be sure that there is no Vray materials. That things make me crashed sometime too.
3)Have you recently install some extra plugins for sketchup? Some of them will make you crashed when you apply materials to object or move etc...
-
@dave r said:
Funny. I can work in SketchUp daily for months and never have a bug splat. They are extremely rare in my experience.
With you, Dave. very rare to get a bugsplat only when I'm playing around with a beta plugin really....
-
@nghminh81 said:
1)Actually Modelling program like CAD, MAX, Rhino and Sketchup always have a limitation of precision. You will never be able to draw an ant standing on earth and flying around the sun. It's computing limitation.
ha.. i just tried that for fun..
drew a sphere 865,000 miles diameter.. then one 93000000 miles away with a diameter of 8000 miles.
(the earth is tiny compared to the sun-- i mean, i knew that already but drawing it really makes it sink in).
things still worked ok at this point.then drew a line 5mm long (ant) on the surface of the smaller sphere.. it worked, and i could select it and rotate around it but i couldn't see it or zoom to it in perspective viewport.. i could work on it fine in the other views though.
regardless, highly impractical for any needs i've come across yet.. might come in handy though when google earth moves to google galaxy and beyond
rhino does have some crazy units to choose from though.. i tried it with miles since it was maybe an in-between of sun & ant size..
-
Angstroms and lightyears, impressive!
-
Thank Jeff for your quick test and correct my point, I've also drawn an ant and our galaxy without any bug.
I had this scaling problem long time ago when I tried to import from Rhino to sketchup 8. It was a complicated part of a washing machine. That bug might happened to only me.
-
@tt_su said:
@notareal said:
Don't recall if Thea for SU had actually crashed SU for me (but I am using a old SU8), still there been reports (at Thea forums) that v-ray for SU and Thea for SU together may result a crash (SU 2013 & OS X). If just Thea for SU where used, everything where fine. Tomasz probably do know better, if there further details on this.
Multiple render engines together has historically been known to increase chance of crashes - usually due to competing observers working at the same time affecting the model.
Sounds feasible. Maybe some more robust method than observers is needed (if not already exist).
Advertisement