Something weird is going on with 2019R1 and Windows 64 bit web apps. I’ve been troubleshooting all morning trying to pin down why a new app I started working on yesterday was crashing every time I tried to run it in the debugger. It’s been a long process of removing method’s modules, classes, etc. Nothing worked. Finally I just rebooted and then started a brand new blank app. It ran fine in both 32 bit and 64 bit. I saved the blank project and then tried again and it crashed immediately. Switched to 32 bit and it would run. So then I closed Xojo and removed all plugins except the default 5 and tried again. It still crashes the blank project. I have repeated this numerous times. One thing I have noticed, after saving the blank project the file size is huge for being blank at 2723 KB.
Hive mind has anyone encountered anything like this?
Tim I’ve been creating fairly large web projects for several years and they average much smaller in size.
Julian, 64 bit window stand alone web app s has bee n my standard for our internal apps for several years. Never had this kind of problem before.
Norman, My next step is to uninstall 2019R1, re-download and reinstall. Looking forward to beers with you next week and hopefully by then I have solved this issue.
Well… uninstalling and reinstalling did not help. On the pus side deleting the 512 and 256 icons reduced the saved file size significantly at 163KB. I never use those sizes in mu apps normally so that explains why the saved size for a blank project surprised me.
Steps:
Open new project using name MyApplication.
Change build settings to Windows and set to 64 Bit
Change Shared Build Settings to Stand Alone
Turn off Hi-DPI
Save project.
Run
Crash Message: DebugMyApplication.exe has stopped working
Well it is definitely machine specific. I installed 2019R1 on a test Windows 10 system and the issue doesn’t repeat itself. Now what the hell did corporate IT remote install to my laptop that is making this happen.
It might also be worth a try running the x64 redist in C:\Program Files\Xojo\Xojo 2019r1\Extras\Windows Runtime\Installers but I can’t see why that would fix an intermittent issue. Anti-virus? Slowly unlocked file?
Well I appear to have resolved the issue by moving the project from my desktop to elsewhere on my local HD. It must be something to do with corporate anti-virus settings that have recently changed. I’ve been working in a different dev environment for the past couple of weeks so it had to have happened recently during that time frame. We were sold in December and our Corporate IT folks have been transitioning a lot of network and endpoint protection systems. Gah! Ack! That was incredibly frustrating!
No. I suspect they tweaked the endpoint protection settings to block something that the debugger is doing on the desktop that it doesn’t block in other user file areas. This wouldn’t be the first time that running the debugger triggers “suspicious activity”. Usually I would get a warning and could create an exclusion but this was just silently blocking and causing a crash.
