Xojo crashes when adding new Method

[DaveS]

I have a large project, and just went to add a new method to it…
No matter what I do, how I name it , the instant I’m done making the header via

1. open an existing MODULE
2. click on METHOD
3. Inspector opens
4. type in name for new METHOD (yes… nothing more than that)
5. click SAVE

CRASH!

This is an application I have been working on for months (started with RS2012, and moved to Xojo on release day, and been working there ever since)

If I restart Xojo and reload the project,… it still compiles and runs … but I cannot add more code to it… and there is ALOT more to go to finish this project

Feedback #27843 - ANY IDEAS???

27843 - Unhandled IOException in BinaryStream.!Create%o<BinaryStream>%o<FolderItem>b

Status: Needs ReviewRank: Not RankedProduct: XojoCategory: IDE » Miscellaneous

Dave SToday at 03:41 PM
Attempting to add a new method to an existing application… Any attempts to create a new method regardless of name, parameters or return value resulted in this crash.
The Module that the method was being added to does have a large number of existing methods (70) or which 1/2 dozen have overload signatures, there are also 47 properties of all datatypes including custom classes, most are global, and 4 structures (simple datatypes that didn’t require the overhead of a class)

However… it was just discovered… that the project will no longer accept new methods ANYWHERE (including in other modules)

This is a BIG SHOW STOPPER

Stack Trace:
BinaryStream.!Create%o%ob
AtomicFileWriter.CreateBinaryFile%o%o
Document.SaveToFile%b%oobo
Document.HandleCommand%b%oo<Commands.Command>
DocWindow.HandleCommand%b%oo<Commands.Command>
StudioMainWindow.StudioMainWindow.HandleCommand%b%o<StudioMainWindow.StudioMainWindow>o<Commands.Command>
Commands.Dispatch%%o<Commands.Command>
Commands.Dispatch%%s
DocWindow._StudioFileSave_Action%b%o
rbframework.dylib$7206
rbframework.dylib$8881
rbframework.dylib$8888
-[NSObject performSelector:withObject:]
-[NSApplication sendAction:to:from:]
-[NSMenuItem _corePerformAction]
-[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:]
-[NSMenu _performActionWithHighlightingForItemAtIndex:sendAccessibilityNotification:]
-[NSMenu performActionForItemAtIndex:]
-[NSMenu _internalPerformActionForItemAtIndex:]
-[NSMenuItem _internalPerformActionThroughMenuIfPossible]
-[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:]
NSSLMMenuEventHandler
_Z22_InvokeEventHandlerUPPP25OpaqueEventHandlerCallRefP14OpaqueEventRefPvPFlS0_S2_S3_E
_ZL23DispatchEventToHandlersP14EventTargetRecP14OpaqueEventRefP14HandlerCallRec
_ZL30SendEventToEventTargetInternalP14OpaqueEventRefP20OpaqueEventTargetRefP14HandlerCallRec
SendEventToEventTarget
_ZL18SendHICommandEventmPK9HICommandmmhPKvP20OpaqueEventTargetRefS5_PP14OpaqueEventRef
SendMenuCommandWithContextAndModifiers
SendMenuItemSelectedEvent
ZL19FinishMenuSelectionP13SelectionDataP10MenuResultS2
_ZL14MenuSelectCoreP8MenuData5PointdmPP13OpaqueMenuRefPt
_HandleMenuSelection2
_HandleMenuSelection
_NSHandleCarbonMenuEvent
_DPSNextEvent
-[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
rbframework.dylib$8991
rbframework.dylib$8992
Delegate.Invoke%%
Application._CallFunctionWithExceptionHandling%%op
rbframework.dylib$4360
rbframework.dylib$8991
-[NSApplication run]
rbframework.dylib$4362
RuntimeRun
REALbasic._RuntimeRun
_Main
% main
_start
start

[DaveS]

Turns out it was an issue with my USB3.0 external drive… I had to dismount, and remount it again.
It would only read… but gave a (-50 error when trying to write)