Segfault when installing Moose baseline #83
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
bug
duplicate
enhancement
help wanted
invalid
linux
macOS
onhold
question
windows
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
pharo/Pulsar#83
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
To reproduce:
uhm... was this working before ?
Yes :(
ok, I was able to reproduce it. This is a hug repository so is a mess, some times it crashes while cloning, some others while loading and even one it loaded 😢
and then I even have something like "The clone location File @ /home/esteban/dev/repo/moosetechnology/FamixTagging already exists"... 🤯
while cloning?? wow, I'm not sure i had this.
Yes, it's big. I can try to load only some parts.
But yes, it used to work
and I thought pulsar had already too many dependencies... 😛
(keeping this here as reference)
@ClotildeToullec wrote in #83 (comment):
yes, this happens when the cloning is aborted in the middle of the process... and then everything is broken the 2nd time.
I have narrowed the problem to an update collision when installing, that makes the repositories view to try to execute an operation (a lot of operations in fact) in the middle of the install process, which of course cause memory violations and BOOM.
I will try to fix it tomorrow :)