How know Who Is calling sub or function

[jury_buono1 (jury buono)]

ok
when I switched from xojo version 2024r3.1 to 2024r4.2 or 2025r5.1 the web application started to freeze(as reported in other posts), it does not close but it freeze and does not respond anymore.
I need to understand where it freeze to fix it because recompiling with 2024r3.1 makes the app much slower so I can’t do it.

To try to understand where the error occurs I have to log every single user activity, but each method can call several other subs or functions both of the webPage and of modules and classes .. and it’s one thing to add a call to a log function (on the whole project) without parameters, a downside is having to call the log function by adding .. name of the caller, method, function or other.

if I don’t need to use code to understand the calling object etc., but I need to use parameter passing, it’s not a matter of adding a function call… but taking the time to add the function call plus all the parameters needed to document the entire tree and this for every object, method, event, sub and function in the entire project…

[Sascha_S]

I assume you can’t just start the server using the debugger, right? (I had to ask…)

[jury_buono1 (jury buono)]

honestly it’s difficult because the application is used by about 3 to 20 people inside and outside the company and I can’t use it in debug mode (or remote debug)

for now I’m launching it on multiple ports (x001, x002,x003—x010) so that when it freezes , the user uses the next port, but it’s a mess

[Tim_Parnell]

@jury_buono1

ok
when I switched from xojo version 2024r3.1 to 2024r4.2 or 2025r5.1 the web application started to freeze(as reported in other posts), it does not close but it freeze and does not respond anymore.
I need to understand where it freeze to fix it because recompiling with 2024r3.1 makes the app much slower so I can’t do it.

You really should have started with that. We shouldn’t have to wildly guess at what you’re doing. Have you searched for the other threads on this issue? There is a known issue that seems to be related to MySQL.

Xojo Web App Just Freezes (no errors, no crashses)

What we’ve seen is a possible race condition when using MySQL (Postgre and other backends are probably fine). The test was just several Thread instances using SelectSQL. Both Console and Web projects were affected. William pushed some fixes to 2025r2, so everyone with access to the betas will be able to start testing it soon to see if it also fixes the issues in their projects.

I am also aware of another issue where Preemptive Threads are suspected to be the cause, but that one is much earlier in the investigation phase and I don’t know of public details on that one.

Next time, start with telling us your issue - not how you think you can fix it. Because yes, some of us are extremely educated in Xojo, even if we didn’t go to Oxford.

[Ricardo_Cruz]

There is a known issue with MySQLCommunityServer that can cause the web app to freeze. It will be fixed in 2025r2, so please try to confirm if it fixes the issue you’re seeing when the beta release cycle begins.

Thank you

[jury_buono1 (jury buono)]

ok thank you, i don’t know if beta 2025r2 resolve because i think that i have no access to beta realses and i can’t find this beta on testers forum page

[AlbertoD]

@jury_buono1

because i think that i have no access to beta realses

@Ricardo_Cruz

when the beta release cycle begins

Maybe the beta release cycle has not begun yet?

[Greg_O]

@jury_buono1

don’t know if beta 2025r2 resolve because i think that i have no access to beta realses

Since you have Pro, you need only send them an email for access.

[AlbertoD]

@Greg_O

send them an email for access

@jury_buono1

i can’t find this beta on testers forum page

Jury said that can’t find the beta on testers forum page, so access is not the problem. Maybe 2025r2 beta release cycle not started yet.

I don’t know if we are allowed to say more here.

[Ricardo_Cruz]

We haven’t released any 2025r2 beta yet.