-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Map (v11.0.6) freezes on Java/FX 17.0.2 shortly after beeing initialized #202
Comments
I got mine randomly freeze too, right now using javafx 17 + java 17 and lastest build of gmapsfx. Try few more times(eg.10 times). I will got 2 ~3 times properly functional, 7~8 times freezes, and if you access GoogleMap again, it will throw MapNotInitializedException. I've tried to renew map by map = googleMapView.getMap();
edit: |
What do you mean by that? I have no liks in the map. |
Were you able to fix this? I'm having the same issue but oddly it only impacts my windows machines...not the mac. EDIT: If anyone else encounters this I solved it by going back to 11.0.2. Not an ideal solution but for my purposes it works fine and maybe it will work for yours too. |
No sorry. Unfortunately I wasn't able to work around this. @dlemmermann Have you ever experienced this behaviour in any of your apps? |
No, I have not. Then again ... not using it extensively at the moment. |
So after running a while on 11.0.2 with no issues now every version except 11.0.7 doesn't load a map at all, and 11.0.7 still has the issue with the map freezing. So we're back where we started on this issue. @dlemmermann any ideas on what I could try? |
The code is rather easy: in the UI code I create an empty container for the map (
mapCard
) and I use the controller to create the map and add Data (markers):The
initResults()
method loads some data from a local database and creates markers. I'm using Kotlin for the application and everything runs in a co routine, but that should not be an issue.What happens is, the map freezes shortly after being initialized, or beeing just for some seconds. No zoomin, no map moving, no marker interaction.
What is notable, though, is that the web container itself still seems to be reacting - I've seen a grey rectanguar border around a marker appearing at least once. So I think, that the input events somehow are not forwarded to the map.
To make sure, it's not something else, I've removed the
initResult()
method as well as the scroll event filter. No change.Since I have no more ideas, I thought raising an issue might be a good idea.
#edit: maybe that's noteworthy: I'm using the classpath variant, the application is not modularized...
The text was updated successfully, but these errors were encountered: