crash at startup on El Capitan 10.11 Beta (15A263e)

User avatar
Salakatika
Posts: 31
Joined: Tue Sep 01, 2015 10:24 pm
Platform: Mac

Sat Sep 05, 2015 12:08 pm Post

KB wrote:Salakatika - do you have any Accessibility options turned on at all?


Nope, none.
Image
"I closed my eyes and tried to bring to mind as many beautiful things as I could. Drawing them closer, holding on to them. Knowing all the while that their lives are fleeting." - Haruki Murakami

Br
Briar Kit
Posts: 1787
Joined: Thu Apr 04, 2013 9:04 am
Platform: Mac

Sat Sep 05, 2015 12:19 pm Post

KB wrote:
Briar Kit wrote:Ergo, you know the exact date of El Cap’s public release? :D


Developers know no more than consumers. But they said Autumn, so we'll start preparing.

Salakatika - do you have any Accessibility options turned on at all?


That's rather hard on the devs; making them rely on their psychic powers. Still, in Kernow, anything magical is possible.
Account closed January 2017

User avatar
KB
Site Admin
Posts: 20719
Joined: Tue Jun 13, 2006 11:23 pm
Platform: Mac
Location: Truro, Cornwall
Contact:

Sat Sep 05, 2015 12:26 pm Post

Salakatika wrote:
KB wrote:Salakatika - do you have any Accessibility options turned on at all?


Nope, none.


Anything strange or different going on with your menus, then? The crash log seems to indicate something in the menu set-up (all Apple internal stuff, nothing in Scrivener's own code) is triggering some sort of preferences or dictionary crash. Any special settings with your menus, either via OS X system preferences or third part tools?

If you go to System Preferences > Users & Groups > Login Items for your account, what is listed there?

Also have a look in /System/Library/StartupItems and /Library/StartupItems to see if anything is in there.

You might also want to try disabling all Extensions via System Preferences temporarily, to see if any of those are having an effect.

Clearly, something your main account is interfering, but it's a case of trying to narrow down what it is.

Briar Kit wrote:That's rather hard on the devs; making them rely on their psychic powers. Still, in Kernow, anything magical is possible.


At some point they release a "Golden Master", at which point you know it's only going to be a couple of weeks or so until release, so that is usually the point at which you know you better get ready to submit to the App Store. Also, they usually forbid any apps built on the beta OS from being submitted to the App Store, and then at some point send out an email to developers saying that they can now submit using the latest OS - which, again, is a sign that release is imminent. We find out the actual day along with everyone else, though.
"You can't waltz in here, use my toaster, and start spouting universal truths without qualification."

User avatar
Salakatika
Posts: 31
Joined: Tue Sep 01, 2015 10:24 pm
Platform: Mac

Sat Sep 05, 2015 1:23 pm Post

KB wrote:Anything strange or different going on with your menus, then? The crash log seems to indicate something in the menu set-up (all Apple internal stuff, nothing in Scrivener's own code) is triggering some sort of preferences or dictionary crash. Any special settings with your menus, either via OS X system preferences or third part tools?


Nothing strange or different that I'm aware of - no special settings or anything like that. It's all basically vanilla. I don't have anything installed that alters these.

KB wrote:If you go to System Preferences > Users & Groups > Login Items for your account, what is listed there?


Just a small handful of apps like Flux, Dropbox, Radium (internet radio), Alfred, etc. I removed all of them and logged back in - no effect.

KB wrote:Also have a look in /System/Library/StartupItems and /Library/StartupItems to see if anything is in there.


The former folder is empty, and the latter only contained a daemon for usage of an Xbox 360 controller with OS X. Removed it - still the same result.

KB wrote:You might also want to try disabling all Extensions via System Preferences temporarily, to see if any of those are having an effect.


Also did this. Still no change. :/

KB wrote:Clearly, something your main account is interfering, but it's a case of trying to narrow down what it is.


I rebooted and tried different things (e.g., running it with/without Scrivener's pre-10.11 Application Support and Preferences files) - at one point, having done all of the above, I was able to get it to start up and run fine, but only once. When I closed it and opened it again, it went back to its normal crashing behaviour. At various points, instead of crashing it has opened with no windows present - if I open a test project, this is what the result is. I should stress that the binder is not supposed to be empty.

Edit: This is my most recent crash.
Image
"I closed my eyes and tried to bring to mind as many beautiful things as I could. Drawing them closer, holding on to them. Knowing all the while that their lives are fleeting." - Haruki Murakami

Br
Briar Kit
Posts: 1787
Joined: Thu Apr 04, 2013 9:04 am
Platform: Mac

Sat Sep 05, 2015 2:55 pm Post

Your crash log mentions Growl.* That hasn't been updated for nearly two years. Could that be the source of the problem?

* Apologies if I have misunderstood the ref in the log!
Account closed January 2017

User avatar
Salakatika
Posts: 31
Joined: Tue Sep 01, 2015 10:24 pm
Platform: Mac

Sat Sep 05, 2015 4:13 pm Post

Not on "my" end - I don't have Growl turned on (and haven't since OS X introduced Notification Centre.) Just to be safe I deleted it, but still no effect. The crash log is referencing a file within Scrivener.app, not on my machine as it were.
Image
"I closed my eyes and tried to bring to mind as many beautiful things as I could. Drawing them closer, holding on to them. Knowing all the while that their lives are fleeting." - Haruki Murakami

User avatar
KB
Site Admin
Posts: 20719
Joined: Tue Jun 13, 2006 11:23 pm
Platform: Mac
Location: Truro, Cornwall
Contact:

Sat Sep 05, 2015 4:59 pm Post

Could you please have a look at the console (/Applications/Utilities/Console.app) and see if any errors get reported there when Scrivener crashes?
"You can't waltz in here, use my toaster, and start spouting universal truths without qualification."

User avatar
Salakatika
Posts: 31
Joined: Tue Sep 01, 2015 10:24 pm
Platform: Mac

Sat Sep 05, 2015 5:14 pm Post

This is what displays in Console.app when I run Scrivener:

Code: Select all

2015-09-05 13:06:35.031 Scrivener[1860]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.0 instead of 10.11.0. This is not a bug in Gestalt -- it is a documented limitation. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.
Call location:
2015-09-05 13:06:35.031 Scrivener[1860]: 0   CarbonCore                          0x9d273f1d ___Gestalt_SystemVersion_block_invoke + 135
2015-09-05 13:06:35.031 Scrivener[1860]: 1   libdispatch.dylib                   0x9321888b _dispatch_client_callout + 50
2015-09-05 13:06:35.031 Scrivener[1860]: 2   libdispatch.dylib                   0x93218767 dispatch_once_f + 78
2015-09-05 13:06:35.031 Scrivener[1860]: 3   libdispatch.dylib                   0x93219ff1 dispatch_once + 31
2015-09-05 13:06:35.031 Scrivener[1860]: 4   CarbonCore                          0x9d1ef9e1 _Gestalt_SystemVersion + 1047
2015-09-05 13:06:35.031 Scrivener[1860]: 5   CarbonCore                          0x9d1ef18a Gestalt + 154
2015-09-05 13:06:35.031 Scrivener[1860]: 6   Menu Extra Enabler                  0x01bacb29 +[RKMEEnabler load] + 40
2015-09-05 13:06:35.038 Scrivener[1860]: objc[1860]: Class DOMHTMLParamElement is implemented in both /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/WebCore and /Library/InputManagers/SafariBlock/SafariBlock.bundle/Contents/MacOS/SafariBlock. One of the two will be used. Which one is undefined.
2015-09-05 13:06:35.038 Scrivener[1860]: objc[1860]: Class WebBaseNetscapePluginView is implemented in both /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebKitLegacy.framework/Versions/A/WebKitLegacy and /Library/InputManagers/SafariBlock/SafariBlock.bundle/Contents/MacOS/SafariBlock. One of the two will be used. Which one is undefined.
2015-09-05 13:06:35.054 diagnosticd[138]: error evaluating process info - pid: 1860, puniqueid: 1860
2015-09-05 13:06:35.056 com.apple.xpc.launchd[1]: (com.literatureandlatte.scrivener2.272032[1860]) Service exited due to signal: Segmentation fault: 11
2015-09-05 13:06:35.111 com.apple.xpc.launchd[1]: (com.apple.ReportCrash[1861]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.ReportCrash
2015-09-05 13:06:35.850 ReportCrash[1861]: Saved crash report for Scrivener[1860] version 2.6 (2.60.5) to /Users/<snip>/Library/Logs/DiagnosticReports/Scrivener_2015-09-05-130635_akatsuki.crash
2015-09-05 13:06:35.860 ReportCrash[1861]: SeedAutoSubmitPreference is 1 via SeedAutoSubmitPreferenceKey
2015-09-05 13:06:35.878 Problem Reporter[1002]: SeedAutoSubmitPreference is 1 via SeedAutoSubmitPreferenceKey


The crash report created is here.
Image
"I closed my eyes and tried to bring to mind as many beautiful things as I could. Drawing them closer, holding on to them. Knowing all the while that their lives are fleeting." - Haruki Murakami

bl
blomert
Posts: 2
Joined: Sun Aug 30, 2015 12:27 pm
Platform: Mac

Sun Sep 06, 2015 4:52 pm Post

So, as said in my first post, Scrivener runs properly with a new useraccount. So i tried to clean up my normal useraccount (e.g. killed growl) deleted Scriveners prefs and Application Support data, redownloaded Scrivener and tried again - no luck.
Then I killed the newest preference under "ByHost" in the Preferences-folder (some loginwindo-plist) and the Scrivener prefs as well.
Retried - and Scrivener started up, asked for Serials etc, I could create a new Project, save it and re-open it, could open "Main Content", everything seemed fine. Then I tried to copy some text into Scriveners "Main Content" - crash. (I will attach the crash report to this mail)
Tried to open again, no luck. Killed the same prefs as before - Scrivener opened up, but crashed when I tried to copy anything into it.
Any help??
Here's the crash report:
Process: Scrivener [3922]
Path: /Applications/Scrivener.app/Contents/MacOS/Scrivener
Identifier: com.literatureandlatte.scrivener2
Version: 2.6 (2.60.5)
Code Type: X86 (Native)
Parent Process: ??? [1]
Responsible: Scrivener [3922]
User ID: 504

Date/Time: 2015-09-06 18:42:04.961 +0200
OS Version: Mac OS X 10.11 (15A279b)
Report Version: 11
Anonymous UUID: 351D43F9-1E0A-D7DA-1303-25A49A139A52


Time Awake Since Boot: 5000 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000a099023d
Exception Note: EXC_CORPSE_NOTIFY

VM Regions Near 0xa099023d:
__LINKEDIT 000000008ff17000-000000008ff2c000 [ 84K] r--/rwx SM=COW /usr/lib/dyld
--> Submap 0000000090000000-00000000a2400000 [292.0M] r--/rwx SM=SHM machine-wide VM submap
mapped file 0000000090000000-0000000090010000 [ 64K] r-x/r-x SM=COW

Application Specific Information:
objc_msgSend() selector name: release


Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x941cb69f objc_msgSend + 31
1 com.apple.CoreFoundation 0x94c3f94f _CFAutoreleasePoolPop + 47
2 com.apple.Foundation 0x9922e478 -[NSAutoreleasePool drain] + 122
3 com.apple.AppKit 0x9aaf1563 -[NSApplication run] + 843
4 com.apple.AppKit 0x9aab7cc8 NSApplicationMain + 1630
5 com.literatureandlatte.scrivener2 0x000023f5 0x1000 + 5109

Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x9e25d8b2 kevent_qos + 10
1 libdispatch.dylib 0x9bc45836 _dispatch_mgr_invoke + 234
2 libdispatch.dylib 0x9bc4540a _dispatch_mgr_thread + 52

Thread 2:: com.apple.NSEventThread
0 libsystem_kernel.dylib 0x9e25607a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9e255464 mach_msg + 68
2 com.apple.CoreFoundation 0x94c83096 __CFRunLoopServiceMachPort + 214
3 com.apple.CoreFoundation 0x94c824a1 __CFRunLoopRun + 1521
4 com.apple.CoreFoundation 0x94c81c46 CFRunLoopRunSpecific + 390
5 com.apple.CoreFoundation 0x94c81aab CFRunLoopRunInMode + 123
6 com.apple.AppKit 0x9ac665c6 _NSEventThread + 291
7 libsystem_pthread.dylib 0x90013794 _pthread_body + 138
8 libsystem_pthread.dylib 0x9001370a _pthread_start + 155
9 libsystem_pthread.dylib 0x90010fa6 thread_start + 34

Thread 3:: JavaScriptCore::Marking
0 libsystem_kernel.dylib 0x9e25c4a2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x90014549 _pthread_cond_wait + 757
2 libsystem_pthread.dylib 0x90016287 pthread_cond_wait$UNIX2003 + 71
3 libc++.1.dylib 0x9d141793 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 63
4 com.apple.JavaScriptCore 0x9c1eca7c JSC::GCThread::waitForNextPhase() + 172
5 com.apple.JavaScriptCore 0x9c1ec8b8 JSC::GCThread::gcThreadMain() + 72
6 com.apple.JavaScriptCore 0x9c76aec2 std::__1::__function::__func<WTF::createThread(void (*)(void*), void*, char const*)::$_0, std::__1::allocator<WTF::createThread(void (*)(void*), void*, char const*)::$_0>, void ()>::operator()() + 18
7 com.apple.JavaScriptCore 0x9c1e130d WTF::threadEntryPoint(void*) + 173
8 com.apple.JavaScriptCore 0x9c1e1240 WTF::wtfThreadEntryPoint(void*) + 16
9 libsystem_pthread.dylib 0x90013794 _pthread_body + 138
10 libsystem_pthread.dylib 0x9001370a _pthread_start + 155
11 libsystem_pthread.dylib 0x90010fa6 thread_start + 34

Thread 4:: JavaScriptCore::Marking
0 libsystem_kernel.dylib 0x9e25c4a2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x90014549 _pthread_cond_wait + 757
2 libsystem_pthread.dylib 0x90016287 pthread_cond_wait$UNIX2003 + 71
3 libc++.1.dylib 0x9d141793 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 63
4 com.apple.JavaScriptCore 0x9c1eca7c JSC::GCThread::waitForNextPhase() + 172
5 com.apple.JavaScriptCore 0x9c1ec8b8 JSC::GCThread::gcThreadMain() + 72
6 com.apple.JavaScriptCore 0x9c76aec2 std::__1::__function::__func<WTF::createThread(void (*)(void*), void*, char const*)::$_0, std::__1::allocator<WTF::createThread(void (*)(void*), void*, char const*)::$_0>, void ()>::operator()() + 18
7 com.apple.JavaScriptCore 0x9c1e130d WTF::threadEntryPoint(void*) + 173
8 com.apple.JavaScriptCore 0x9c1e1240 WTF::wtfThreadEntryPoint(void*) + 16
9 libsystem_pthread.dylib 0x90013794 _pthread_body + 138
10 libsystem_pthread.dylib 0x9001370a _pthread_start + 155
11 libsystem_pthread.dylib 0x90010fa6 thread_start + 34

Thread 5:: JavaScriptCore::Marking
0 libsystem_kernel.dylib 0x9e25c4a2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x90014549 _pthread_cond_wait + 757
2 libsystem_pthread.dylib 0x90016287 pthread_cond_wait$UNIX2003 + 71
3 libc++.1.dylib 0x9d141793 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 63
4 com.apple.JavaScriptCore 0x9c1eca7c JSC::GCThread::waitForNextPhase() + 172
5 com.apple.JavaScriptCore 0x9c1ec8b8 JSC::GCThread::gcThreadMain() + 72
6 com.apple.JavaScriptCore 0x9c76aec2 std::__1::__function::__func<WTF::createThread(void (*)(void*), void*, char const*)::$_0, std::__1::allocator<WTF::createThread(void (*)(void*), void*, char const*)::$_0>, void ()>::operator()() + 18
7 com.apple.JavaScriptCore 0x9c1e130d WTF::threadEntryPoint(void*) + 173
8 com.apple.JavaScriptCore 0x9c1e1240 WTF::wtfThreadEntryPoint(void*) + 16
9 libsystem_pthread.dylib 0x90013794 _pthread_body + 138
10 libsystem_pthread.dylib 0x9001370a _pthread_start + 155
11 libsystem_pthread.dylib 0x90010fa6 thread_start + 34

Thread 6:
0 libsystem_kernel.dylib 0x9e25ce16 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x9001335f _pthread_wqthread + 1289
2 libsystem_pthread.dylib 0x90010f82 start_wqthread + 34

Thread 7:
0 libsystem_kernel.dylib 0x9e25ce16 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x9001335f _pthread_wqthread + 1289
2 libsystem_pthread.dylib 0x90010f82 start_wqthread + 34

Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x020224e0 ebx: 0x03001010 ecx: 0x941e7c22 edx: 0xa099021d
edi: 0x941ccfdf esi: 0x03001000 ebp: 0xbffffbd8 esp: 0xbffff998
ss: 0x00000023 efl: 0x00010202 eip: 0x941cb69f cs: 0x0000001b
ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f
cr2: 0x0b9be000

Logical CPU: 0
Error Code: 0x00100170
Trap Number: 132

User avatar
nontroppo
Posts: 1174
Joined: Mon Mar 05, 2007 5:22 pm
Platform: Mac
Location: Airstrip One

Thu Sep 10, 2015 11:40 am Post

El Capitan has gone Golden Master!!!

User avatar
Salakatika
Posts: 31
Joined: Tue Sep 01, 2015 10:24 pm
Platform: Mac

Thu Sep 10, 2015 1:27 pm Post

It has, but sadly, Scrivener still crashes for me on the GM candidate, same as before.
Image
"I closed my eyes and tried to bring to mind as many beautiful things as I could. Drawing them closer, holding on to them. Knowing all the while that their lives are fleeting." - Haruki Murakami

User avatar
KB
Site Admin
Posts: 20719
Joined: Tue Jun 13, 2006 11:23 pm
Platform: Mac
Location: Truro, Cornwall
Contact:

Thu Sep 10, 2015 2:10 pm Post

At this point, I recommend doing a clean reinstall with the El Capitan GM candidate - back up everything, wipe your machine, install the GM candidate and reinstall everything. This is a huge pain, but I recommend it anyway if you've been using a beta OS, regardless of problems with Scrivener. Every time there's an OS update, we see some users encounter gremlins until they do a clean install, and this problem is exacerbated with installing OS betas beforehand.
"You can't waltz in here, use my toaster, and start spouting universal truths without qualification."

User avatar
Salakatika
Posts: 31
Joined: Tue Sep 01, 2015 10:24 pm
Platform: Mac

Thu Sep 10, 2015 2:27 pm Post

If the next version of Scrivener still crashes on 10.11, that's what I plan to do - but it would be an all-day project, which is something I just don't have the time for right now. I used to do clean reinstalls every few years just to keep things running smoothly but haven't done it since I got this machine last year. I usually did them during the summer when I was still a university student, which was convenient. Life's a little busier now!

I'm not sure the problem was "exacerbated" by installing a beta version beforehand; if it still crashes on the GM, it's likely that had I waited until public release, the same problem would have still occurred when I booted up Scrivener for the first time. Aside from not being able to blame it on me (and the other users who have this problem), I don't think anything would have been different in that scenario.
Image
"I closed my eyes and tried to bring to mind as many beautiful things as I could. Drawing them closer, holding on to them. Knowing all the while that their lives are fleeting." - Haruki Murakami

User avatar
KB
Site Admin
Posts: 20719
Joined: Tue Jun 13, 2006 11:23 pm
Platform: Mac
Location: Truro, Cornwall
Contact:

Thu Sep 10, 2015 3:14 pm Post

Salakatika wrote:Aside from not being able to blame it on me (and the other users who have this problem), I don't think anything would have been different in that scenario.


I don't think anyone's blaming it on you - but from what I can see, neither is it down to Scrivener. Something pertaining to the updates you've run has messed up something on your machine which is interfering with Scrivener. All of the crash logs are deep OS X preferences crashes. And given that you said Scrivener works fine in a new account (is that still true?), that means that something in your main account is interfering with it. It may be that some third-party software you have installed has caused problems with El Capitan, and that is affecting Scrivener, but obviously, without having direct access to your machine it's impossible to say, which is why I'm suggesting drastic measures.

Really, I'd much rather find the source of the crash or what is interfering, but we've tried everything I can think of - disabling all login items and so on. If I Google for crashes similar to yours, they all come up wit El Capitan beta crashes that have affected random applications.

Salakatika wrote:I'm not sure the problem was "exacerbated" by installing a beta version beforehand; if it still crashes on the GM, it's likely that had I waited until public release, the same problem would have still occurred when I booted up Scrivener for the first time.


This isn't necessarily the case. Problems often creep in when updating OS X, which is why clean installs often fix things, and obviously, when using public betas, you run several upgrades with bugs over several months.

We are having a few users with this crash, though, and all of them say it doesn't affect other user accounts, so it would be nice to narrow down what the trigger is. Some more things to check:

1. You mentioned you tried a safe boot and that didn't fix the issue, but did Scrivener run while running in safe mode?

2. Run Activity Monitor in your main account and in the user account where Scrivener works fine. Compare them and let me know any processes that are running in your main account but not in the other account. One of these processes could be the culprit. Back in your main account, use the "X" button in Activity Monitor to force quite any processes that aren't run on your other account, and then try running Scrivener. (If that works, try narrowing it down to the specific process.)

3. Take a look at the following directories:
~/Library/LaunchAgents
/System/Library/LaunchAgents
/System/Library/LaunchDaemons

4. Have a look in System Preferences for any extra preference panes there.

5. Check out any differences in the user account login items and Security & Privacy settings between your user accounts.

6. Try disallowing access to Contacts with Security & Privacy then start Scrivener.

7. Try running something like CleanMyMac to zap any gremlins that knows about.

8. Is Scrivener installed in your /Applications directory, incidentally?

Looking at your earlier Console log, some things to check:

This line:

2015-09-05 13:06:35.031 Scrivener[1860]: 6 Menu Extra Enabler 0x01bacb29 +[RKMEEnabler load] + 40

What is "Menu Extra Enabler"? Menu and contextual menu plugins are notorious for causing crashes (although they usually occur while an app is running). Try uninstalling that.

Take a look in these folders:

/Library/InputManagers
~/Library/Contextual Menu Items/

(Note: check both the main /Library folder and the user account ~/Library folder, which you can access by holding Option down as you open the "Go" menu in Finder.)

Drag anything in those folders to the Desktop (so that you can restore them afterwards) and try launching Scrivener once those folders are empty. (Another line on your Console log also reports something problematic in the /Library/InputManagers folder.)

All the best,
Keith
"You can't waltz in here, use my toaster, and start spouting universal truths without qualification."

F4
F451
Posts: 44
Joined: Thu Jan 25, 2007 4:03 am

Thu Sep 10, 2015 3:54 pm Post

I'm running into this:

Application Specific Information:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSDictionaryI length]: unrecognized selector sent to instance 0x1c0b5d0'

El Capitan GM

At this point I'd rather purchase the upgrade to the next version of Scrivener (no matter what stage the next version is currently undergoing) and be done with it as use of this current version is simply nonexistent.