How know Who Is calling sub or function

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…

1 Like

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

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

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.

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.

7 Likes

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

4 Likes

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

Maybe the beta release cycle has not begun yet?

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

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.

1 Like

We haven’t released any 2025r2 beta yet.

OK there is a way, but it involves some work.

Lets suppose every method is defined like this:

myMethod (caller as string, param2 as myThing, param3 as myThing)

myMethod includes a line like

writeMyLog CurrentMethodName + “ was called by “ + caller

Then. for every method that calls myMethod, the call is then:

result = myMethod(CurrentMethodName, param2, param3)

This will then give you a log of calls to myMethod, listing the method that did it, and in the order they occurred.

There are better ways that were discussed last year.

1 Like

Maybe, but I searched as far as 31-12-2024 and found no related title.

IMHO: a link to the discussion thread would be far usable for the OP.

Then you scrolled right past it. I have said so many times throughout this thread that it’s such a bad idea and it means you have a bad code design. I am not pointing you straight to it.