Relate to #3338
With a fresh install.

Tested on Win10 (and linux); same steps with fresh install-- no repro! tab is closing OK.
@halfbrained
(that was on last beta from /c/ folder).
Jairo, can u try another ways of tab-closing?
No such problem on Ubuntu 18 or Win7 for me
Testing again with /c release.
Same with a fresh download.
If I change the lexer to JSON^ I can close the tab, but If a change again to JSON, the tab remains unclosable.
as I said I also used clean Cud, no settings, and cannot repeat that. I tried linux+win10.
Jairo, so you used the 1-core VM? so it seems it messed the work. could you change VM settings to have 2-3 cores? ie CPUs.
@MiroslavMatas
You have Windows10, right? Could you help us to test the same issue please!
Jairo, so you used the 1-core VM? so it seems it messed the work. could you change VM settings to have 2-3 cores? ie CPUs.
I have no VMs, I am using directly an PC with Windows10:
Processor Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 2401 Mhz, _2 Core(s), 4 Logical Processor(s)_
okay, so we cannot find the reason. yet.
But yes Alex, the only way to close the tab is changing to JSON^, that is why I think the "problem" happens when CudaText is not finishing in right way the lexer painting thread, you know when you use threads you need to ensure close or terminate them in order to give the control to the main thread, the UI thread in this case.
I found the 'bad code', working to fix
reproduced somehow. and solved? beta in /c folder updated. pls test.

No yet 😠I mean, with this version the problem persists.
strange. I renamed the files on server. maybe you got cached files...
That is my idea if you can upload files increasing the build number, but let me try with another browser.
uploaded with a new file name.
Works for me just the first time, after reopen the user.json I couldn't not close again by a second time. :(
I need to move away from home, I will test restarting Windows, considering something is cached in Windows, but I can sure the first time I could close the tab.
Something happened, I missed one previous comment, but basically for me worked ok just the first time after I downloaded, but in the second time I got the same problem. I had to restart the PC considering if something was cached by Windows (One handle maybe).
Now I tested again and all seems is OK, I will be testing more in the next hours.
_@MiroslavMatas_
You have Windows10, right? Could you help us to test the same issue please!