Bug or not
Posted: Thu Aug 11, 2022 9:29 pm
Hi, I already asked about it once and as far as I remember the answer would be that there is a problem in Windows. Unfortunately, I couldn't find the topic.
Just now, I quite accidentally noticed that this happens due to frequent calls to TCustomResourceHandler.Create.
In the procedure I have a flag TCustomResourceHandler.ProcessRequest which interrupts
Chromium_On Get Resource Handler...
if LoadRSR then resourcehandler := Handler; since after the document is loaded, the elements are loaded from the network.
And if you do this repeatedly, problems begin in Windows. The way the clipboard stops working, the context menu is buggy and many programs stop working. Only a reboot will help.
Previously, I thought that this was due to the repeated re-creation of the browser, perhaps it is) But if you use one instance, the problem will be the same.
I took a similar method to replace LoadString, which was removed from CEF. This option would also suit if it were not for this problem.
What am I doing wrong?
Windows is buggy

Just now, I quite accidentally noticed that this happens due to frequent calls to TCustomResourceHandler.Create.
In the procedure I have a flag TCustomResourceHandler.ProcessRequest which interrupts
Chromium_On Get Resource Handler...
if LoadRSR then resourcehandler := Handler; since after the document is loaded, the elements are loaded from the network.
And if you do this repeatedly, problems begin in Windows. The way the clipboard stops working, the context menu is buggy and many programs stop working. Only a reboot will help.
Previously, I thought that this was due to the repeated re-creation of the browser, perhaps it is) But if you use one instance, the problem will be the same.
I took a similar method to replace LoadString, which was removed from CEF. This option would also suit if it were not for this problem.
What am I doing wrong?
Windows is buggy
