apache / apache/grails-intellij-plugin

Working with Grails stops IDE system job (linux)

Open
#228 0 comments 0 reactions 0 assignees View on GitHub
bug imported-from-youtrack
Dominant language
Java
Stars
17
Forks
4
Avg merge
5d 15h
Merged PRs (30d)
4

Description

Downloaded Grails 3.0.9 from [https://grails.org/download.html](https://grails.org/download.html), unzipped into my local system (Fedora).

Run the IDE like this:

> /some-path/idea-IU-143.761/bin/idea.sh &

In the IDE: Settings / ... / Grails / "Grails SDK Home" field: specified proper path.

Opened a project. Created new Grails 3 module with this SDK.
After several seconds and some expected UI effects the IDE window is frozen: no changes, no reaction to the input.
In the system shell I press Enter and get this:

> [1]+ Stopped /some-path/idea-IU-143.761/bin/idea.sh

I.e. it's not a JVM deadlock. The IDE **system job** has been stopped.

Using `fg` and `bg` commands I can resume the process. But every switch to IDE window causes the stop again.
Later, when Grails process(es) completes, the IDE is Ok again.

I suspect that some command from Grails shell scripts causes the effect, but could not find what command.
System shell (console) contains no more messages, idea.log doesn't contain obvious errors.
IDEA 143.761.

---

*Imported from [IDEA-147812](https://youtrack.jetbrains.com/issue/IDEA-147812) · Type: Bug · Votes: 0*
*Comments, attachments, dates and reporter are not part of the export — follow the link above for the full history.*

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce with Grails 3.0.9 on Fedora using IDEA 143.761 and the shown idea.sh command, then create a Grails 3 module with the configured SDK. Start by comparing the Grails shell scripts, idea.log, and system-shell behavior during the freeze. Done means the IDE system job no longer stops when Grails processes run.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, linux
Domain
devtools, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.