The code is posted as follows, in case there is something wrong with the way APIs are called: const git = require('nodegit')Ĭonst repoInstance = await (rootPath)Ĭonst repoRemote = await repoInstance.getRemote('origin')Ĭonst author = (username, email)Ĭonst cred = (username, password)Ĭonst signature = '\nauto commit -ignore'Ĭonst commitMessage = `Modify file $`Īwait repoInstance.stageFilemode(relPath, true)Īwait repoInstance. The message that would be more accurate is: 'The operating system kernel has terminated the process before startup with signal SIGSEGV, segmentation fault.' Could we. This isnt quite true because 'startup' never happened. Reinstalling node and node modules didn’t work either, but I’m guessing it’s still most likely a compatibility issue with node. (In reply to Keith Seitz from comment 6) > During startup program terminated with signal SIGSEGV, Segmentation fault. I even tried to monitor v8 heap/CPU usage, nothing suspicious was found though.
Real trouble is this happens randomly, sometimes after 2 or 3 times of API calling, other times just straight-down crashes on the first call.
At first I thought it might be problems with Remote#push, then I found out that commit and stage are also causing node to crash with the same error. I went through all related issues closed/open.
0 kommentar(er)
