Yesterday I upgraded a customer site from 4Dv17R4 to 4Dv17R6 (243126).
This is a compiled database. But on the 4D remote client running the web server, the debugger window opens once in a while. Which is of course blocking the web app.
Though the debugger indicates ‘TRACE Command’ in red in the left bottom corner, there is no TRACE command involved. Anyway TRACE should do nothing in a compiled db, neither should the debugger window be activated.
As far as I can see, the piece of code shown in the code pane is coming from a text file which is executed using PROCESS 4D TAGS
The call chain shows External Call Back / On Web Connection
What is going on?
32209574;“Debugger opens on compiled db…”[/]