After having started to use xojo (2014r2, OS X 10.9.4) seriously in an attempt to port one of my larger apps (>900,000 lines including its plugin in C), I must agree with past reports of frequent crashes from some users . Maybe once an hour is a little exaggerated, but not much. Happens with various ops, like messing with properties in the navigator and usually during a compile. Example crash log would be:
Have others experienced this? I find xojo far less stable than RB/RS (and yes I’d file a report if I could actually get Feedback to download, install and run, which I cannot). From my experience anyway, xojo has significant stability issues.
Interesting. That is possible, I am working from a 8GB laptop. However, with a fast SSD I would’ve thought that swapping to VM would never allow this occur.
So here’s another one since we last “spoke” (this is the frequency of crashes I am faced with):
2014-08-15 11:39:27.411 PM Xojo[9734]: Xojo(9734,0xa07a11a8) malloc: *** mach_vm_map(size=69304320) failed (error code=3)
*** error: can’t allocate region
*** set a breakpoint in malloc_error_break to debug
What Greg says makes sense and it is an out-of-mem issue, BUT, not because I don’t have enough RAM/VM, but because xojo runs out of 32-bit addressing space AND does not trap failed mallocs. So this is a problem because if xojo is 32 bit and cannot function with a 32-bit space, this is not good I would think.
But the crashes continue Norm: 2 more after a few hours on a different machine. So I think xojo has a significant problem (and I would file reports if I could get Feedback installed, also failed on 2 machines):
This happens with every new version of Feedback on my two machines.
Workaround: Open 164_Feedback.dmg with Disk Utility and launch the installer manually.
[quote=121851:@Peter Stys]But the crashes continue Norm: 2 more after a few hours on a different machine. So I think xojo has a significant problem (and I would file reports if I could get Feedback installed, also failed on 2 machines): [/quote]
Go to the downloads page on our site, click Extras, and download Feedback from there.
We have four developers in our office and we all experience crashes with the XOJO IDE. The last version of RB that we used (RB2012r2) seemed pretty solid and we experience very few creates, but XOJO seems to have memory leaks that result in crashes.
We have converted a couple of pretty sizable applications and the crashes seem to be unavoidable. The only thing I can tell you is let CMD-S (CTRL-S on Windows) be your best friend. We also do NOT rely on any code recovery that XOJO tries to do after a crash. Absolutely unreliable.
We have found no corollary between the number of apps open, the size of the app, or plugins, and whether you are coding, debuting, or building. Happens everywhere.
The only thing that seems to make sense is memory leaks because on a clean reboot and restart of XOJO, we never have a crash no matter what we do until we’ve been working in it for some time. Generally, an hour or two.
No, we did not file a feedback report because the last time this issue came up on the forums, everyone said it was rock solid, so that meant it must be us, right?
More food for thought. A couple of us work exclusively in OSX and a couple of us work exclusively in Windows (64 bit). We both experience about the same number of crashes. I’ve tried working in the Windows IDE and find it unusable after working in OSX. Still no CTRL-C, CTRL-V… have to use the menus to copy and paste. Crazy!
From what you are telling I’d say this seems to be project related. Also an indication for that is that no stability problems have been discussed on this forum lately as far as I can recall. Random shot: an outdated plugin.
For me, earlier versions of the IDE (2012rXXX) were terrible memory leakers (something like 200MB per compile) so I could only compile about 10 times before the IDE crashed. I’m not seeing those sorts of issues in Xojo lately, so this does sound like something specific to your use.
And I work on the IDE all day every day usually 10+ hours a day and never have this
I’ve been running the IDE for about 4 days solid without crashes or restarts
YMMV
[quote=121853:@Eli Ott]This happens with every new version of Feedback on my two machines.
Workaround: Open 164_Feedback.dmg with Disk Utility and launch the installer manually.[/quote]
That’s exactly what I did, and that’s the error I got, trying to open the dmg from Finder. Just FYI, but this is off-topic.
Not sure what you mean Eli: xojo crashes towards the end of a build-run operation. My last one did not even register a crash in the Console. What was logged is curious and may/may not be informative:
2014-08-17 2:08:53.600 AM Xojo[74864]: objc[74864]: Class XOJBevelButton is implemented in both /Users/pstys/Dropbox/LabStuff_DropBox/Development/Xojo 2014 Release 2.1/Xojo.app/Contents/Frameworks/RBAppearancePak.xojo_plugin_0.dylib and /Users/pstys/Dropbox/LabStuff_DropBox/Development/Xojo 2014 Release 2.1/Xojo.app/Contents/Resources/Internal Plugins/RBAppearancePak.xojo_plugin/Appearance Pak/Build Resources/Mac Cocoa/AppearancePakCocoa.dylib. One of the two will be used. Which one is undefined.
2014-08-17 2:08:53.600 AM Xojo[74864]: objc[74864]: Class XOJImageWell is implemented in both /Users/pstys/Dropbox/LabStuff_DropBox/Development/Xojo 2014 Release 2.1/Xojo.app/Contents/Frameworks/RBAppearancePak.xojo_plugin_0.dylib and /Users/pstys/Dropbox/LabStuff_DropBox/Development/Xojo 2014 Release 2.1/Xojo.app/Contents/Resources/Internal Plugins/RBAppearancePak.xojo_plugin/Appearance Pak/Build Resources/Mac Cocoa/AppearancePakCocoa.dylib. One of the two will be used. Which one is undefined.
2014-08-17 2:08:53.600 AM Xojo[74864]: objc[74864]: Class XOJChasingArrows is implemented in both /Users/pstys/Dropbox/LabStuff_DropBox/Development/Xojo 2014 Release 2.1/Xojo.app/Contents/Frameworks/RBAppearancePak.xojo_plugin_0.dylib and /Users/pstys/Dropbox/LabStuff_DropBox/Development/Xojo 2014 Release 2.1/Xojo.app/Contents/Resources/Internal Plugins/RBAppearancePak.xojo_plugin/Appearance Pak/Build Resources/Mac Cocoa/AppearancePakCocoa.dylib. One of the two will be used. Which one is undefined.
2014-08-17 2:08:53.601 AM Xojo[74864]: objc[74864]: Class XOJDisclosureTriangle is implemented in both /Users/pstys/Dropbox/LabStuff_DropBox/Development/Xojo 2014 Release 2.1/Xojo.app/Contents/Frameworks/RBAppearancePak.xojo_plugin_0.dylib and /Users/pstys/Dropbox/LabStuff_DropBox/Development/Xojo 2014 Release 2.1/Xojo.app/Contents/Resources/Internal Plugins/RBAppearancePak.xojo_plugin/Appearance Pak/Build Resources/Mac Cocoa/AppearancePakCocoa.dylib. One of the two will be used. Which one is undefined.
2014-08-17 2:08:53.601 AM Xojo[74864]: objc[74864]: Class XOJLittleArrows is implemented in both /Users/pstys/Dropbox/LabStuff_DropBox/Development/Xojo 2014 Release 2.1/Xojo.app/Contents/Frameworks/RBAppearancePak.xojo_plugin_0.dylib and /Users/pstys/Dropbox/LabStuff_DropBox/Development/Xojo 2014 Release 2.1/Xojo.app/Contents/Resources/Internal Plugins/RBAppearancePak.xojo_plugin/Appearance Pak/Build Resources/Mac Cocoa/AppearancePakCocoa.dylib. One of the two will be used. Which one is undefined.
2014-08-17 2:08:53.601 AM Xojo[74864]: objc[74864]: Class XOJSeparator is implemented in both /Users/pstys/Dropbox/LabStuff_DropBox/Development/Xojo 2014 Release 2.1/Xojo.app/Contents/Frameworks/RBAppearancePak.xojo_plugin_0.dylib and /Users/pstys/Dropbox/LabStuff_DropBox/Development/Xojo 2014 Release 2.1/Xojo.app/Contents/Resources/Internal Plugins/RBAppearancePak.xojo_plugin/Appearance Pak/Build Resources/Mac Cocoa/AppearancePakCocoa.dylib. One of the two will be used. Which one is undefined.
2014-08-17 2:08:53.630 AM Xojo[74864]: objc[74864]: Class XOJSegmentedControl is implemented in both /Users/pstys/Dropbox/LabStuff_DropBox/Development/Xojo 2014 Release 2.1/Xojo.app/Contents/Frameworks/RBGUIKit.xojo_plugin_0.dylib and /Users/pstys/Dropbox/LabStuff_DropBox/Development/Xojo 2014 Release 2.1/Xojo.app/Contents/Resources/Internal Plugins/RBGUIKit.xojo_plugin/GUIKit/Build Resources/Mac Cocoa/GUIKitCocoa.dylib. One of the two will be used. Which one is undefined.
2014-08-17 2:08:53.630 AM Xojo[74864]: objc[74864]: Class XOJGUIKit_ActionTarget is implemented in both /Users/pstys/Dropbox/LabStuff_DropBox/Development/Xojo 2014 Release 2.1/Xojo.app/Contents/Frameworks/RBGUIKit.xojo_plugin_0.dylib and /Users/pstys/Dropbox/LabStuff_DropBox/Development/Xojo 2014 Release 2.1/Xojo.app/Contents/Resources/Internal Plugins/RBGUIKit.xojo_plugin/GUIKit/Build Resources/Mac Cocoa/GUIKitCocoa.dylib. One of the two will be used. Which one is undefined.
2014-08-17 2:08:53.641 AM Xojo[74864]: objc[74864]: Class XOJWebKitDelegate is implemented in both /Users/pstys/Dropbox/LabStuff_DropBox/Development/Xojo 2014 Release 2.1/Xojo.app/Contents/Frameworks/RBHTMLViewer.xojo_plugin_0.dylib and /Users/pstys/Dropbox/LabStuff_DropBox/Development/Xojo 2014 Release 2.1/Xojo.app/Contents/Resources/Internal Plugins/RBHTMLViewer.xojo_plugin/HTMLViewer/Build Resources/Mac Cocoa/HTMLViewerCocoa.dylib. One of the two will be used. Which one is undefined.
2014-08-17 2:08:54.672 AM Xojo[74864]: [RB] Unable to load plugin CocoaTestPlugin. xojo_plugin
2014-08-17 2:08:54.673 AM Xojo[74864]: [RB] Unable to load plugin Build Resources
2014-08-17 2:08:54.681 AM Xojo[74864]: [RB] Unable to load plugin IDE Resources
2014-08-17 2:08:54.681 AM Xojo[74864]: [RB] Unable to load plugin FFT_CocoaPlugin. xojo_plugin
2014-08-17 2:08:54.681 AM Xojo[74864]: [RB] Unable to load plugin Build Resources
2014-08-17 2:08:54.690 AM Xojo[74864]: [RB] Unable to load plugin IDE Resources
2014-08-17 2:08:54.690 AM Xojo[74864]: [RB] Unable to load plugin ImageTrakPlugin. xojo_plugin
2014-08-17 2:08:54.690 AM Xojo[74864]: [RB] Unable to load plugin Build Resources
2014-08-17 2:08:54.803 AM Xojo[74864]: [RB] Unable to load plugin IDE Resources
2014-08-17 2:08:54.803 AM Xojo[74864]: [RB] Unable to load plugin MBS140Plugins
I frequently get the ‘Unable to load plugin xxx’ messages. Not sure what this is all about as the plugins must be loaded because the built app runs a successfully calls functions within the plugins. XOJO crashed right after the above but there was no further entry.
