That was it! Issue resolved :). I ran my test twice - 40 out 40
successful. I also checked it once more manually in the node console and
in Ezra Project and it works without issues now!
Thank you so much, Troy.
Now I can switch to the latest SWORD trunk with Ezra Project!
Best regards,
Tobias
untar now updated. Thanks for your time with this.
On 10/17/20 4:36 PM, Tobias Klein wrote:
Updated to SVN Rev. 3813.
Still hanging here:
#0 0x56143eb2f28c in sword::FileMgr::sysOpen(sword::FileDesc*) ()
#1 0x56143eb18b0b in sword::FileDesc::getFd() ()
#2 0x56143eb9323b in (an
Updated to SVN Rev. 3813.
Still hanging here:
#0 0x56143eb2f28c in sword::FileMgr::sysOpen(sword::FileDesc*) ()
#1 0x56143eb18b0b in sword::FileDesc::getFd() ()
#2 0x56143eb9323b in (anonymous namespace)::untar(void*, char
const*) ()
#3 0x56143eb93b60 in sword::ZipCompress:
Dear Troy,
Thank you so much for the help and all your work on this. Unfortunately
the issue is still not resolved for me based on your latest commits.
I have n threads that all run InstallMgr::refreshRemoteSource. n
corresponds to the number of repositories available, so it's currently 10.
T
OK Tobias,
Give it a go when you have a chance and let me know.
Troy
On 10/17/20 12:16 PM, Troy A. Griffitts wrote:
The unTarGZ is also a new method and it looks like it is using the
default file handle pool functionality of FileMgr, from looking at
your stack trace. Give me about an hour an
The unTarGZ is also a new method and it looks like it is using the default file
handle pool functionality of FileMgr, from looking at your stack trace. Give me
about an hour and I'll have a chance to take a look at it. Good news is that
it's not having trouble in the CURLFTPTransport. I have the
Dear Troy,
Thank you so much for the help and all your work on this. Unfortunately
the issue is still not resolved for me based on your latest commits.
I have n threads that all run InstallMgr::refreshRemoteSource. n
corresponds to the number of repositories available, so it's currently 10.
T
Dear Tobias,
Thank you for all the great information. This enabled me to isolate the
change which caused the issue.
So, for a bit of background, SWORD has no calls to mark critical
sections which might be problematic for re-entrant usage. This has been
due to the many implementations of th
I managed to get a backtrace to a segmentation fault using GDB.
It seems like the crash is happening in sword::FileMgr::open( ...
The starting point is sword::InstallMgr::refreshRemoteSource as I was
writing before.
Best regards,
Tobias
Program received signal SIGSEGV, Segmentation fault.
[S
Hi Troy,
I tested more SVN revisions of SWORD trunk (starting from my stable
version until I hit the bug) and I can now say that
SVN Rev. 3759 is the last SVN revision that works without hanging for
the below mentioned scenario. (20 out of 20 tests successful)
SVN Rev. 3760 is the first SVN
I'll see whether I can collect a stack trace. It may take some time
until I have it.
The multi-threaded "remote source refreshing" worked without issues
until recently.
Here is the code of the function that does the actual work in a thread.
See
https://github.com/tobias-klein/node-sword-inte
Any luck getting a stack trace on crash?
Regarding the "multitheaded mode", I'd have to get a bit more information as to
exactly how you are sharing SWORD objects across your threads. Generally, as a
rule, you shouldn't. We recommend a separate instance of SWMgr per thread and
that probably goe
Hi Troy,
I'm using curl on all three platforms.
Regarding the timeout configuration I have not changed anything yet, to
make this configurable in Ezra Project is still on my todo list.
I just checked on Linux.
With the old version (May 18th 2020) no hanging or crash in 10 out of 10
times.
WI
Hi Tobias,
What transport library are you building with? ftplib or curl?
Have you changed the value of our new timeout from the default, I believe we
decided on, 10 seconds?
Troy
On October 12, 2020 6:46:54 PM GMT+02:00, Tobias Klein
wrote:
>Hi Troy,
>
>In my latest Ezra Project builds using
Hi Troy,
In my latest Ezra Project builds using SWORD trunk I’ve been noticing random
„hangs“ and crashes related to "updating remote sources“. I suppose it must be
around InstallMgr::refreshRemoteSource.
This was still rock solid when using SWORD trunk from May 18th 2020, but not so
any more
15 matches
Mail list logo
