Xojo IDE fails on startup

2017 R2.1. I was using Xojo as of last weekend, fire it up today get

Xojo had stopped working and it crashes

Windows 7 64 bit, as I said it was working last weekend.

Also sometimes it will pop up

Runtime Error
D:\GO\pipelines\Release-Frameworks-New\Build\Universal\stringmap.
h:192
Failure Condition: nullptr==mIterators

Did you do the usual troubleshooting?

  • Restarted the computer?
  • Tried another computer?
  • Tried another user on the same computer?
  • Removed all plugins?
  • Deleted all caches? Check the forum and the documentation where this stuff is located for Windows.

What did you change between last week and this week? I searched the forum for “stringmap” and found only an old post from me but this was for a built app and not the IDE.

Yes
No
No other user, just me at home
No plugins, I have the Desktop Version for Windows
No, and I will check into it, it was displaying a roaming directory

I’ve had corrupted projects that do that to me.

I have alot of personal time invested in this one, really frustrated

Is it crashing on startup? Or later when doing something else?

On startup

I also tried uninstalling and re-installing, same issue

Other suggestions:

  • Try 2017 Release 3
  • Create a new user account and try running Xojo from there.

If that works, I will have to pay for the upgrade, which I really don’t want to do

Well, no. Those are just additional troubleshooting steps that might pinpoint corrupt preferences. Certainly, trying 2017r2.1 in a new user account does not require you to upgrade anything.

When you say New User Account, you lost me, how is that tied to running Xojo?

A new Windows user account. Xojo preferences are saved per user account. So if you try it in a new user account, new preferences will be created. If it works there then that could indicate preferences in the problem account are corrupt. If it also doesn’t work in a new user account then the problem is elsewhere. It gives us an additional data point to help you troubleshoot.

I created a new account with my work email, same issue.

I tried uninstalling and re-installing to to avail. I wonder if there are any lingering registry keys I need to clean up as well

I installed 2017 R3 and it’s fine. But I really don’t want to pay for an upgrade

And going back to the error:
D:\GO\pipelines\Release-Frameworks-New\Build\Universal\stringmap.
h:192

Why is it looking for a D: drive?
I don’t have that drive letter designated anywhere on my desktop

open your dos box and assign c = d

[quote=370318:@Brent Eamer]And going back to the error:
D:\GO\pipelines\Release-Frameworks-New\Build\Universal\stringmap.
h:192

Why is it looking for a D: drive?
I don’t have that drive letter designated anywhere on my desktop[/quote]
I’m told this is some sort of internal error, but we are puzzled as to why you would be seeing it.

Would it be possible for you to generate a Windows mini dump and attach it to a Feedback case for the engineers to look at?

Instructions on how to do this are here: http://developer.xojo.com/techinfo/creating-crash-dumps