You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2023-02-09 05:16:21
EAccessViolation at TUriTreeNode.RewriteUri
Today I got the following AV:
20230209 05111254 00000000AD4F394E & EXCOS EAccessViolation (c0000005) [] at cc2926
mORMot.Net.Server.pas TUriTreeNode.RewriteUri (1729)
mormot.core.os.windows.inc GetModuleHandle (394)
mormot.core.os.windows.inc GetModuleHandle (394)
System.pas TMonitor.RemoveWaiter (20266)
System.Classes.pas ResetSyncEvent (15692)
System.pas @InitResStringImports (24792)It happened only once with yesterdays mORMot2 sources. I cannot reproduce or give any hints as to when or why that happend. I simply started a mORMot-server and the AV happened. Restarting the server was without any problems.
I'll keep my eyes peeled, but wanted to put it out here in case anyone sees somethings similar or has any idea.
Sorry for being vague, but I can't tell more at this time :-(
Regards,
Daniel
Offline
#2 2023-02-09 08:05:48
Re: EAccessViolation at TUriTreeNode.RewriteUri
Did you try to enable the logs in verbose mode?
It could help to see which URI was called, and the exact context.
And it won't slow down the process too much, even on production.
Currently I don't have any idea what was going on, even looking back and reviewing this part of the code.
https://github.com/synopse/mORMot2/commit/bbfe4650 is perhaps cleaner, but I doubt the previous code was not correct.
Offline
#4 2023-02-09 10:00:41
Re: EAccessViolation at TUriTreeNode.RewriteUri
At startup, it does not make much sense... this method should not be called outside of an external client request, and an URI rewrite.
TUriTreeNode.RewriteUri is never called in a regular mORMot server.
Did you use the new URI rewrite feature?
That is, did you define some alternate routes?
Or did you have some browser opened toward the server, requesting e.g. the favicon resource?
Offline
Pages: 1