Closed aberenguel closed 5 months ago
Hi @aberenguel, thanks for reporting this! I don't see any reference to the GraphTask above, but anyway a stop condition to avoid an infinite recursion is mandatory! I'll merge your fix shortly, thanks!
Sorry @aberenguel, looking better at the stacktrace, I see the "Finishing graph CSVs...". But WhatsApp parsing shouldn't be running at this point... Just to better understand the issue, have this WA DB triggered a timeout? Maybe it is the same case @wladimirleite reported here: https://github.com/sepinf-inc/IPED/issues/1916#issuecomment-1894583484 ???
Just to better understand the issue, have this WA DB triggered a timeout?
After a lot of time the processing finished, but the chats did not appeared in case.
Maybe it is the same case @wladimirleite reported here: #1916 (comment) ???
Yes. It is the same case. But @wladimirleite processed the WhatsApp database isolated in order to test the PR #2048
@aberenguel, are the WhatsApp databases shown in the processed case? Is "timeout" property set to true for them? I just started the processing of the complete UFDR, using the WhatsApp enhancements branch.
@aberenguel, are the WhatsApp databases shown in the processed case?
The database files (msgstore.db, etc) were in the case. But the children chats were not there.
Ok I think it triggered a timeout. In that case the parsing thread receives an interrupt signal, but continues to run if the code does not check it. That is the only way I can imagine some WA parsing stacktrace being printed when Graph CSVs are generated at the end of processing.
Please let me know if the commit I pushed to your PR is enough to fix the recursion issue or not.
The database files (msgstore.db, etc) were in the case. But the children chats were not there.
What about the timeout property? 😀 If it is set to true, it would explain both behaviors (no chats and the setThumbData loop). If that is the case, give a try with the WhatsApp PR. It should solve the timeout (although it is a very large DB and will take a while to be processed).
Is "timeout" property set to true for them?
Sorry! I didn't see. I will be able to check tomorrow.
I'm using IPED 4.2 (master branch).
I've caught these exceptions bellow that make the "Finishing graph CSVs" step takes a huge time to finish.
In summary the method
Message.setThumbData()
calls itself recursively but there is no stopping condition in this specific case.