I have a win10 i5 with 40g ram and 2022r4. I have a project for Win desktop where Im reading in a customer table in json from one api endpoint, parsing it up and resending it to another endpoint. pretty simple stuff and for testing, I wrote the incoming json to file so I dont have to be connected all the time while i get the parsing act together. The json out file has 21,152 lines that make up 196 records. Xojo reads the file in so fast I cant even tell the time it takes. So then I made a much smaller json file containing 6 records worth of data to do some meticulous mapping checks etc. Reading the super shortened version takes 6 seconds - its only 152 lines!? Going between the short and long files its the same - the long one is instant and the short one takes 6 seconds. It also takes about 10-12 seconds to get from running code to stopped in the debugger. The IDE is unresponsive for the 1-12 seconds. It takes so long I get distracted and its killing my productivity. It wasnt doing this a day or two ago. Ive tried it with 2022r1 and its the same. Ive tried rebooting, clearing the cache everything i could find people saying might help. So weird…any ideas? I will just test with the long one i guess but waiting for the IDE to stop in teh debugger is torture.
What has changed since that day or two:
- Did you changed the code
- Were patches applied to the OS
- Is the project file local on the computer running Xojo
?
What is the OS you run and the version ? If you are on Windows, when there are patches waiting to be installed, that may leave the OS in an unstable state because not all OS components are in sync. If that is the case, apply the patches and try again.
Also, please check the OS logs for clues that may provide an explanation.
Thanks Gilles, I will try to keep digging. It is now changing in lag time. The weird thing is that if I set a break point, it takes 20-30 seconds to break into the debugger the first time then its fast to subsequent break points. If you stop and rerun, it takes 20-30 seconds to break again. This is not complicated stuff either so its really a mystery and so so so very annoying. here im wasting hours debugging my debugging…I’ve never seen this in the mac ide but the last time i did a project all on win I noticed a lot of weird behavior too. This project was having really aweful autocomplete and then all of a sudden it came alive and is great. Things like that make me crazy.
Have you run profiling to see where the slowdown is?
In less scientific guessing, a 20-30 second slowdown specific to Windows for accessing a file kind of sounds like anti-malware software getting in the way.
Thanks Tim, I will check those out. I have not run the profiler so that might help. I tend to agree as Ive jumped to a different project now on the same machine and its snappy as ever. Im not a win person so Ill have to dig into how to turn off the malware/virous stuff.
I disabled all win defender and theres no change at all unfortunately… Im not sure how to check if theres any other malware/virous stuf on this box but ill try some more. So weird.
From where do you load the small file, from a network location?
No they are both in a documents sub folder at the same level. Quite odd. They were both created sql server queries. The smaller is simply a subset of the first 8 entries, copy and pasted into a new document in Sublime. I even tried repeating that process to make sure I didnt inadvertantly introduce some kind of bad character. Again, Im not a Win guy so maybe I dont know soemting critical but I sure cant find it. The other side of this is far worse - even on other projects now, its taking 20-30 seconds to get to the first breakpoint. Just torture.
Earlier last week, I did upgrade the RAM from a single 8g module to add an additional 32g module. However, the machine ran great without this debug lag for 4-5 days…
I put the 32g in the slot the 8 was in and the 8 in the other slot below it (was empty). Could that be a problem? it shows 40g in the system settings. I dont know if that caused any issues but nothing else I use seems affected. I could maybe pull the old 8 or try try swappin git back to the way it was I guess.
I was able to solve the opening small vs large file difference by diabling WindowsDefender via some hacks and a reboot. So the anti-malware suggestion here was probably the cause fo that weirdness. Thanks a ton for both @Tim_Parnell - i also didnt realize the profiler was now built in to the IDE. The last time I used aprofiler in RB it was a 3rd party plug-in if irc correctly… long ago. Its very nice, very nice.
So now I am still trying to figure out why the 20-30 second lag in getting into the debugger for the first breakpoint.
I am not sure what I have wrong in my setup but I guess I have to abandon windows as a development environment - it sjust too painful to use. It just took 90 seconds to pause the code in the debugger on a relativley new project. Still taking 20-30 seconds to get to a break point on the first one, then its normal but what torture…
What about the provided examples ? Did you try some ?
Greta idea - I just did but its the same huge lag between the action and the break in the debugger. 20-30 seconds. Brutal. I dont know what could cause such a thing but it makes xojo unusable on win as far Im concerned. I was thinking I might go whole hog on windows until this…
When I view a variable in the debugger that contains a large amount of data, I get a pause. So I avoid it. I wonder if that is something related?
Also, it could still be windows defender doing something.
Right, like a big dict or something I do too but this is just stopping the ‘run’ and it takes like a minute. The first break in teh debugger is faster but still like 20-30 seconds
Weird. I don’t see this and I am using windows exclusively.