Any issues with Mojave?

Answered

I haven't been running the macOS Mojave beta. It's looking imminent. Are there any issues with IntelliJ and Java development?

2
38 comments

So far we did not get any problems reported specifically for macOS Mojave version.

-1
Avatar
Permanently deleted user

After upgrading to the official version of Mojave, idea will take a long time to open the loading interface.

4
Avatar
Permanently deleted user

Pycharm is lagging while running code that would run just fine before the Mojave update.

0
Avatar
Permanently deleted user

i noticed a very very very minor issue, when creating the windows (sometimes it happens with the main window and pretty much with all the dialogs) there's a quick yellow flash which happens only the first time you open the window, i'm attaching a screenshot to show what i mean, the flash is very very quick (i'm talking milliseconds) but very noticeable :)

 

1
Avatar
Permanently deleted user

After upgrading to Mojave, now my IntelliJ takes nearly 5 min to load. quite annoying

0
Avatar
Permanently deleted user

Main window dissapeared after selecting project, so I have to restart multiple time to get the main window reappear again.

0
Avatar
Permanently deleted user

Pychram says: Сannot Run Git
xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun

after update to Mojeve

6
Avatar
Permanently deleted user

I upgraded last night and found that after using it a while I can no longer enter characters.  I can click to move the cursor, but when I type nothing happens.  If I switch to another app I can type fine, so I am assuming that this is an IntelliJ issue.  Restarting IntelliJ fixed it until it just happened the second time today.

7
Avatar
Permanently deleted user

David Krcil,

I had that too. That is just that the command line tools need to be re-installed with "xcode-select --install".  That was a quick fix for me.

0
Avatar
Permanently deleted user

Ah, so pressing and holding a key brings up the accented character selector and then freezes IntelliJ.  Then, pressing and holding a character to bring up the selector again unfreezes IntelliJ so I can type again without restarting.  Got it.  This is a good workaround for the present.

1
Avatar
Permanently deleted user

DataGrip is also much slower switching between databases, running queries, and showing up results. Overall, the experience feels laggy, which was not the case before. I've checked the activity monitor to see if there was any strange CPU or memory spikes, but it seems to match on average the consumption it had on the previous OS.

6

When debugging tests Intellj now hangs for several seconds (10 seconds), these are test with no external dependencies and should run in less than 1 second. 

Intellj version: 2018.2.5 (Ultimate)

Running Java tests

1

You may have a problem with DNS, see the following documents:

https://youtrack.jetbrains.com/issue/IDEA-157303
http://stackoverflow.com/a/39698914/104891

git clone https://github.com/thoeni/inetTester
java -jar ./bin/inetTester.jar

Find the hostname that's output from the .jar.

`sudo nano /etc/hosts` and add these two entries.

127.0.0.1 <output-host-name>.local
::1 <output-host-name>.local

 

2

Thank you, that fixed it, very fast and good reply to my problem :-)

0
Avatar
Permanently deleted user

Updated to Mojave and immediately started seeing terrible performance in DataGrip while getting result sets.

Initial try at adding the entries to hosts didn't resolve anything but I'll try a few more things to see if it works, just wanted to add another report here as a warning against updating to Mojave if you like DataGrip.

1

Please report at https://youtrack.jetbrains.com/issues/DBE with the logs/dumps and CPU snapshots. It may be not specific to Mojave.

0
Avatar
Permanently deleted user

Updated to Mojave, launching Java debug in IntelijIdea will be stuck for several minutes, how to resolve this problem.

2

Since installing Mojave, I have been having trouble with basic debugging commands:  when I use the  "step over" or "step into" commands, the program immediately executes to the next break point or completion, rather than just one line of code.  Oddly, the "run to cursor" command works, and so I have had to resort to using that, though it is rather cumbersome to have to keep moving the cursor then the run command.  I'm currently running Mojave 10.14.1 Beta and PyCharm 2018.2.4 on a MacBook Pro (15" 2017).  Any help/pointers would be greatly appreciated.  Thanks.

1

I'm noticing the yellow flash problem in other Java applications. It is timing dependent. The yellow may be a debugging aid that was mistakenly left on in Mojave. It interacts badly with a known Java bug.

0
Avatar
Permanently deleted user

Checking back in due to more research findings. The bug that started with Mojave for me is 100% reproducible as long as the result set it has to render is wide. It seems to be directly tied to scrolling across result sets that are too big for the monitor.

0
Avatar
Permanently deleted user

Intellij is very slow and keeps repeating the Indexing very frequently. Gets stuck very frequently even when 6-8GB ram is free and 4 GB is allocated to Intellij. Debugging is very slow too.

1

Please raise a ticket at https://youtrack.jetbrains.com/issues with complete log folder compressed including ThreadDump directory: https://intellij-support.jetbrains.com/hc/en-us/articles/207241085

0

yes intellij slows down mojave to the point that it needs a restart. 2 instances of Intellij amplifies it.

1
Avatar
Permanently deleted user

Try disabling all Plugins and see if that helps with the performance problems.

0
Avatar
Permanently deleted user

Updating to macOS 10.14.2 and resetting the NVRAM fixed the slow scrolling issue for me.

The update alone didn't cure it, so it may be that resetting the NVRAM is enough.

1
Avatar
Permanently deleted user

Thanks Dean! Only time will tell if this is a permanent fix but resetting NVRAM caused scrolling to go back to normal. DataGrip is usable again.

0

Before upgrade , IDEA parse "VM options: location=/data/apps/tao.sar" is ok. 

After upgrade, IDEA parse "VM options: location=/data/apps/tao.sar" is not ok : run main Class, Java class found "location=.data.apps.tao.sar"

0

Please sign in to leave a comment.