In the last 4-5 weeks I noticed more and more crashes.
I switch a lot between Id’s, open and close the desigern and admin client several times. Sometimes nsd fires after switching id’s or after saving a form or out of the blue…
I removed all plugins and widgets and even with them removed the crashes happen.
I run two VMs to get access to two IDs at once, since Lotus destroyed the ability to run multiple simultaneous clients. If you have the capacity to run a VM you may be able to work around the crashing.
I average 2 crashes or hangs a day. And then when I restart Designer, I have to sit there watching “Restore metafiles” and “Initializing Java Tooling” for at least 5 minutes.
Just one of the burdens that we developers have to carry.
The 8.5.1 Designer Client leaves a lot to be desired. It is slow, unstable, crashes when interacting with the Admin client, etc. And I don’t even do much developing. It really isn’t a very solid product yet…kinda like an alpha release. I wish I could enable a “UseBasicDesigner=1” ini parm to bring back the good ol’ days until they get it stabilized…
Glad it’s not just me. I’ve experienced the perfect storm of having designer open, lotusscript debug on, and attempting to open the Admin client. Locked to the point I had to do a Window restart just to get it to forgive me.
Why is IBM ignoring the issue that “Initializing Java Tooling” can take up to 10 minutes for a local database opening in designer? Am I being unreasonable here?
Luckily I’ve upgraded to 8.5.2 which probably shaved a good 2 seconds off the time required for this.
It seems that IBM is starting to ignore the crashing problems, the slow startup problems. Used to be that IBM / Lotus Notes customer service was far superior to Microsoft, now I don’t know anymore.I have spent the last 3 hours today just trying to get my client to startup without crashing.
Subject: “Initializing Java Tooling” takes 5-10 minutes to load in Designer
I agree about the problem with starting up Domino Designer. I don’t know what it is actually loading or waiting for, but the “Initializing Java Tooling” message in the progress sits there for 5-10 minutes before it releases Designer so that I can do anything with it.
I managed to open a browser, navigate to here, log in and write this message without the loading of Designer having completed yet.
The problem is so bad that I took to leaving Designer up and running all the time, even when I might not need it for days, rather than endure the pain of launching it when I need it and waiting for it to do whatever the h*ll it does when it launches.
Why can’t this be fixed? Is Designer pulling in modules over the 'net or something? What could possibly take that long to complete when simply launching an application?
IBM, when will this be fixed? We’ve been putting up with it for several years, and the new versions don’t change the behavior.
I get frequent crashes not just of the DDE client but also of the Notes client. In my case, there seems to be a strong link between the use of the debugger and frequent crashes. Since I’m fond of using the debugger, it’s just something I have learned to live unhappily with.