Saturday, March 21, 2015

Re: Compiling permutation hangs ?

I'm having a similar issue though I haven't checked the stacktraces. An existing, long working, large GWT application hangs at permutation 0... in 2.6.1 and the problem also exists in 2.7. Any ideas on how to follow up on this?

On Tuesday, November 18, 2014 at 3:20:38 PM UTC-8, Ed wrote:
@Jens, thanks​
I just tried again with more memory, namely:
----
<extraJvmArgs>-Xms2G -Xmx2G -Xss1024k -XX:PermSize=512m -XX:MaxPermSize=1024m -Dgwt.persistentunitcache=false</extraJvmArgs>
----

And got the following output snippet below with jstack after about 30 min. It's still busy, but doesn't complet...

I am not sure if I need to set the MAVEN_OPTS during CLI maven usage ? (I do when running the job through Jenkins). I tired it before, but still not luck, maybe I used it wrong...
I am not sure if the gwt maven plugin does fork a new thread/process that uses part of the total memory assigned to maven, or that it uses the memory as specified in the plugin config (as above).
I can imagine that if the assigned total maven mem is Max let say 512MB, setting the mem max 2G in the plugin config might have no effect as it's more then maven can allow the plugin to use...


----
"In-process PermutationWorker 0" prio=10 tid=0x00007f4bd86dc800 nid=0x6fcc runnable [0x00007f4bc60be000]
   java.lang.Thread.State: RUNNABLE
        at com.google.gwt.dev.js.ast.JsConditional.traverse(JsConditional.java:87)
        at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:468)
        at com.google.gwt.dev.js.ast.JsModVisitor$NodeContext.traverse(JsModVisitor.java:153)
        at com.google.gwt.dev.js.ast.JsModVisitor.doAccept(JsModVisitor.java:176)
        at com.google.gwt.dev.js.ast.JsVisitor.accept(JsVisitor.java:109)
        at com.google.gwt.dev.js.ast.JsBinaryOperation.traverse(JsBinaryOperation.java:118)
        at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:468)
        at com.google.gwt.dev.js.ast.JsModVisitor$NodeContext.traverse(JsModVisitor.java:153)
        at com.google.gwt.dev.js.ast.JsModVisitor.doAccept(JsModVisitor.java:176)
        at com.google.gwt.dev.js.ast.JsVisitor.accept(JsVisitor.java:109)
        at com.google.gwt.dev.js.ast.JsExprStmt.traverse(JsExprStmt.java:42)
        at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:468)
        at com.google.gwt.dev.js.ast.JsModVisitor$ListContext.traverse(JsModVisitor.java:80)
        at com.google.gwt.dev.js.ast.JsModVisitor.doAcceptWithInsertRemove(JsModVisitor.java:197)
        at com.google.gwt.dev.js.ast.JsVisitor.acceptWithInsertRemove(JsVisitor.java:121)
        at com.google.gwt.dev.js.ast.JsBlock.traverse(JsBlock.java:48)
        at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:468)
        at com.google.gwt.dev.js.ast.JsModVisitor$NodeContext.traverse(JsModVisitor.java:153)
        at com.google.gwt.dev.js.ast.JsModVisitor.doAccept(JsModVisitor.java:176)
        at com.google.gwt.dev.js.ast.JsVisitor.accept(JsVisitor.java:109)
---

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment