Step 4 Out of Memory, and step 5 can not work, how can I get DebugMethodName-0.0.1-SNAPSHOT.jar?

[zoubaihan]

Hello, When I running step 4 "java -cp "target/dependency/*" -Xmx8g edu.lu.uni.serval.renamed.methods.Main", it would throw exception as follow:

[31147.205s][warning][os,thread] Failed to start thread - pthread_create failed (EAGAIN) for attributes: stacksize: 1024k, guardsize: 0k, detached.
[ERROR] [01/14/2022 18:51:20.315] [methodNames-system-akka.actor.default-dispatcher-5] [akka.actor.ActorSystemImpl(methodNames-system)] Uncaught error from thread [methodNames-system-akka.actor.default-dispatcher-5] shutting down JVM since 'akka.jvm-exit-on-fatal-error' is enabled
java.lang.OutOfMemoryError: unable to create native thread: possibly out of memory or process/resource limits reached
at java.base/java.lang.Thread.start0(Native Method)
at java.base/java.lang.Thread.start(Thread.java:798)
at scala.concurrent.forkjoin.ForkJoinPool.tryAddWorker(ForkJoinPool.java:1672)
at scala.concurrent.forkjoin.ForkJoinPool.signalWork(ForkJoinPool.java:1966)
at scala.concurrent.forkjoin.ForkJoinPool.externalPush(ForkJoinPool.java:1829)
at scala.concurrent.forkjoin.ForkJoinPool.execute(ForkJoinPool.java:2955)
at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinPool.execute(AbstractDispatcher.scala:395)
at akka.dispatch.ExecutorServiceDelegate$class.execute(ThreadPoolBuilder.scala:211)
at akka.dispatch.Dispatcher$LazyExecutorServiceDelegate.execute(Dispatcher.scala:39)
at akka.dispatch.Dispatcher.registerForExecution(Dispatcher.scala:115)
at akka.dispatch.Dispatcher.dispatch(Dispatcher.scala:55)
at akka.actor.dungeon.Dispatch$class.sendMessage(Dispatch.scala:144)
at akka.actor.ActorCell.sendMessage(ActorCell.scala:374)
at akka.actor.Cell$class.sendMessage(ActorCell.scala:295)
at akka.actor.ActorCell.sendMessage(ActorCell.scala:374)
at akka.actor.LocalActorRef.$bang(ActorRef.scala:404)
at akka.actor.ActorRef.tell(ActorRef.scala:128)
at akka.routing.ActorRefRoutee.send(Router.scala:45)
at akka.routing.Router.send(Router.scala:123)
at akka.routing.Router.route(Router.scala:116)
at akka.routing.RoutedActorCell.sendMessage(RoutedActorCell.scala:141)
at akka.actor.Cell$class.sendMessage(ActorCell.scala:295)
at akka.actor.ActorCell.sendMessage(ActorCell.scala:374)
at akka.actor.RepointableActorRef.$bang(RepointableActorRef.scala:171)
at akka.actor.ActorRef.tell(ActorRef.scala:128)
at edu.lu.uni.serval.renamed.methods.ParseActor.onReceive(ParseActor.java:110)
at akka.actor.UntypedActor$$anonfun$receive$1.applyOrElse(UntypedActor.scala:165)
at akka.actor.Actor$class.aroundReceive(Actor.scala:484)
at akka.actor.UntypedActor.aroundReceive(UntypedActor.scala:95)
at akka.actor.ActorCell.receiveMessage(ActorCell.scala:526)
at akka.actor.ActorCell.invoke(ActorCell.scala:495)
at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:257)
at akka.dispatch.Mailbox.run(Mailbox.scala:224)
at akka.dispatch.Mailbox.exec(Mailbox.scala:234)
at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)

I try to allocate more memory, but even I allocate 190G memory to this java command as ""java -cp "target/dependency/*" -Xmx190g edu.lu.uni.serval.renamed.methods.Main"", unfortunately, it still throws exception "out of memory".
And if I ignore the error upon, when I running the step 5 “mvn package”，another exception is throwed. No matter I use windows or linux, the error is the same as follow:

at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:566)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)

[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

If anyone have the jar file "DebugMethodName-0.0.1-SNAPSHOT.jar", maybe I can skip this bug? Could anyone share me his jar file?
Have you ever seen these error? Could anyone please teach me how to fix it?
Now I don't know where the bug located in.
Any brother could help me?

[Kui-Liu]

Hello @zoubaihan , for step-4, you could collect the renamed methods from the repo one by one, if you do not have enough computing resource.
For the issue of step-5, I have no idea as well. I do not know what is the problem. If you follow the steps presented in README, I think you should run it successfully.