Today I installed Scratch on my computer. Unfortunately, I received this message
Sorry but the VM has crashed
Exception code: COOOOOO5
Current byte code 226
Primitive index: 521
Please help
Veronica Pereyra Mora
from Peru
Offline
I'll need this information to best help you:
o Operating System
o OS Version
o Scratch Version
o Anything else that was not done exactly as it should.
Offline
Same thing different Byte Code and Primitive index.
Exception code: COOOOOO5
Current Byte Code: 23
Primitive index: 113
Happens with every machine we tried it on.
Dell Optiplex GX620
Windows XP Svc pack 3
Scratch 1.4
Reinstall was not effective in the test group and is time-prohibitive en masse anyway due to a large number of machines involved.
App crashes without even loading any files other than the default theme. Scratch crashes either directly after loading, as it is exiting, or when one attempts to save files to various locations, without any files other than the default load files (the cat) being in play.
Note that the issue, tho chronic, appears randomly, as it will be possible to load once, and then not the next time, or to save to a location, and then not again. Relogging the user on the computer seems to fix the issue for the first load of the app, but invariably the Fatal VM Error occurs. The app seemed to work at first but the problem appeared relatively soon after it's introduction.
Security restrictions do exist on these machines but the users have Read/Write permissions to the scratch folder and to all file save locations which are actually used.
Last edited by Longsight (2010-03-19 10:53:45)
Offline
This should really be in Troubleshooting...
Offline
Thought it was. i had been in Troubleshooting but was searching for an answer so probably got skipped over to wrong location. Note that I did not start the thread.
I would indeed like to request that this be moved, if such is possible and appropriate.
Last edited by Longsight (2010-03-19 10:56:18)
Offline
It is possible.
May i suggest re-opening the program again? Maybe that might work.
Offline
This has already been done. In fact we even logged the users on and off of the machines, and rebooted a few boxes as well, with only very limited success. The issue is random in its manifestation (crashes either at log, or at save, or at quit) but shows up fairly rapidly, if not immediately after a reload.
Last edited by Longsight (2010-03-19 12:49:39)
Offline
Longsight wrote:
This has already been done. In fact we even logged the users on and off of the machines, and rebooted a few boxes as well, with only very limited success. The issue is random in its manifestation (crashes either at log, or at save, or at quit) but shows up fairly rapidly, if not immediately after a reload.
Have you made a thread in the troubleshooting forum? This isn't an advanced topic.
Offline
I hadn't wanted to open an additional thread on an extant open topic as such is generally considered rude (I can't count the number of "Use the Search feature!!" replies I've seen on various threads when other people posted duplicate questions).
Re-posting would be a double post and thus also probably be against the "polite" forum rules. If an admin does not move the post by Monday I will re-post in Troubleshooting.
If an admin does move this post, feel free to remove the extraneous "please move the post" requests from the thread.
Last edited by Longsight (2010-03-19 15:32:59)
Offline
Just giving options on what to do, its just people dont tend to post here when they have glitches.
Offline