-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
p4-fusion
1.13 core dumps with certain configs
#67
Comments
Making the lookahead only 1 in total may suggest a problem with memory accesses during the scheduling and sharing of memory across multiple tasks running at the same time. Might have to look deeper with a stack trace or attach a debugger and see what exactly is exploding here. Once I find time for this issue, I would start with the seeing the difference in execution across threads with lookAhead set to 1 VS 2, and try to find any anomalies. (Note to self) |
I con corroborate this. Using the following config I get a crash with lookAhead=2000 and no crash with lookAhead=1.
|
Occasional core dumps with 1.13, most of them SIGSEGV
core dumps do not happen all of the time, but this command loops five times; a core dump usually happens several times:
Note that
<perforce user>
needs to be replaced with a value user for the Perforce instance,<user ticket>
needs to be replaced with the correct ticket for the user,<perforce host>
replaced with the actual Perforce host + port #, and<depot name>
with the depot name or path, including the leading//
and trailing/
.Test plan
Connect to
gitserver
via a terminal and run the above command. If usingp4-fusion
1.13, it will fail some or all of the time with core dumps.Example output:
If using
p4-fusion
1.12, the output will be allreturn code: 0
, like this one:Not that it helps here, but changing
lookAhead
to1
seems to stop the core dumps, at the cost of cloning speed.The text was updated successfully, but these errors were encountered: