This site requires JavaScript, please enable it in your browser!
Greenfoot back
tannercyost
tannercyost wrote ...

2017/1/26

Greenfoot crashes on startup

tannercyost tannercyost

2017/1/26

#
Hi everyone, I am trying to get started using Greenfoot for a class I am taking and am running into an issue which I cannot seem to solve by myself. I was running Greenfoot just fine for a few days and then after doing some of the labs for my class it refuses to open. It seems like it is crashing Java when it tries to open and I have tried reinstalling both Java and Greenfoot multiple times to no avail. The attached screenshot is what happens when I try and open Greenfoot. At this point, I have to actually enter the task manager and end the greenfoot process or else it just keeps trying to open. Does anyone have any ideas? Is there some sort of cache for Greenfoot I need to clear?
danpost danpost

2017/1/27

#
Try moving the project file outside of the greenfoot/scenarios folder and see if it will open then ('it' being greenfoot -- not the project). If you are using a 'public static void main(String args)' method, that may be the cause. I will explain later if need be.
tannercyost tannercyost

2017/1/27

#
The project I'm trying to open is already outside of the greenfoot folder, and I've tried moving it around several times to several places and it still just doesn't work. Here's the debug log file: Greenfoot run started: Thu Jan 26 17:50:14 PST 2017 Greenfoot version: 3.0.4 Java version 1.8.0_92 Virtual machine: Java HotSpot(TM) Client VM 25.92-b14 (Oracle Corporation) Running on: Windows 10 10.0 (x86) Java Home: C:\Program Files (x86)\Greenfoot\jdk\jre ---- Opening project: C:\Program Files (x86)\Greenfoot\lib\greenfoot\startupProject 1485481815911: Listening for JDWP connection on address: javadebug Connected to debug VM via dt_shmem transport... Communication with debug VM fully established. 1485481820003: Listening for JDWP connection on address: javadebug Connected to debug VM via dt_shmem transport... Communication with debug VM fully established. 1485481822791: Listening for JDWP connection on address: javadebug Connected to debug VM via dt_shmem transport... Communication with debug VM fully established. 1485481825192: Listening for JDWP connection on address: javadebug Connected to debug VM via dt_shmem transport... Communication with debug VM fully established. 1485481827946: Listening for JDWP connection on address: javadebug Connected to debug VM via dt_shmem transport... Communication with debug VM fully established. Also the image didn't embed so here's a direct link to it. For now I am just running Greenfoot through a virtual machine running Ubuntu and it's working fine but it's a less than ideal solution haha.
danpost danpost

2017/1/27

#
The image did not imbed because you used a URL for a webpage and not to the image itself. Maybe you could download one of the Standalone versions onto a USB flash drive.
tannercyost tannercyost

2017/1/27

#
I was able to figure it out. Debugging it using Visual Studio pointed to Nvidia drivers, so I uninstalled them and it ran fine. Reinstalling the same version reproduced the error, so I just rolled back to the version before and Greenfoot seems to be working just fine now. Thanks for your help danpost!
Valiworld Valiworld

2017/2/4

#
So i have the same problem like tannercyost and I just deinstall my nvidia drivers(all) and than itll work?
danpost danpost

2017/2/4

#
Valiworld wrote...
So i have the same problem like tannercyost and I just deinstall my nvidia drivers(all) and than itll work?
I do not know; but, it looks like more than that was done:
Reinstalling the same version reproduced the error, so I just rolled back to the version before and Greenfoot seems to be working just fine now.
Valiworld Valiworld

2017/2/4

#
OMFG it doesnt even work with the first ever version of greenfoot pls some1 save me
Valiworld Valiworld

2017/2/5

#
ye when i open 3.0.3 this error appears again and i hava no clue why pls help
Super_Hippo Super_Hippo

2017/2/5

#
I think it wasn't an older Greenfoot version but an older Nvidia driver.
mehanix mehanix

2017/2/6

#
I'm not too sure if this is related, but I'm also running Nvidia drivers and Greenfoot is very unstable for me with issues compiling, saving to disk, and graphical issues on the code text editor (text remaining imprinted on the screen when scrolling or glitching out).
Super_Hippo Super_Hippo

2017/2/6

#
With 3.1.0, it sometimes happens to me that class code is invisible and I have to mark it with the mouse (or reload) to make it visible. Sometimes this also happens with the error output in the console and there, it is not possible to make it visible then. I am not sure if this is the same problem though because I never have a problem that the loading screen freezes and the program doesn't start at all.
black_a85 black_a85

2017/2/17

#
hi, I solved it by removing the Physx (Nvidia Control Panel) and the Geforce experience programs, now Greenfoot run fine and i have the driver installed so I can still play games without troubles
You need to login to post a reply.