1.4.2 is giving me time erors

[Kommi]

Ever since I installed 1.4.2 I have had this error happen with my animation loop. What happens is that the first time I fire up my game it runs fine. But subsequent times it loads a white screen. If I alt - tab and then click on it again then the prog crashes giving me the following error:

An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION (0xc0000005) occurred at PC=0x182D7D76
Function=Java_sun_print_Win32PrintJob_endPrintRawData+0x1D42
Library=C:\j2sdk1.4.2\jre\bin\awt.dll

Current Java thread:
     at sun.awt.windows.Win32BackBufferSurfaceData.initSurface(Native Method)
     at sun.awt.windows.Win32BackBufferSurfaceData.createData(Win32BackBufferSurfaceData.java:49)
     at sun.awt.windows.Win32BackBuffer.createHWData(Win32BackBuffer.java:28)
     at sun.awt.windows.WVolatileImage.initAcceleratedBackground(WVolatileImage.java:100)
     at sun.awt.image.SunVolatileImage.<init>(SunVolatileImage.java:86)
     at sun.awt.windows.WVolatileImage.<init>(WVolatileImage.java:72)
     at sun.awt.windows.Win32BackBuffer.<init>(Win32BackBuffer.java:20)
     at sun.awt.windows.WComponentPeer.createBackBuffer(WComponentPeer.java:734)
     - locked <0x1051f358> (a sun.awt.windows.WFramePeer)
     at sun.awt.windows.WComponentPeer.replaceSurfaceData(WComponentPeer.java:324)
     - locked <0x1051f358> (a sun.awt.windows.WFramePeer)
     - locked <0x1050f7a8> (a java.awt.Component$AWTTreeLock)
     at sun.awt.windows.WComponentPeer$2.run(WComponentPeer.java:333)
     at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:454)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)

I am using a native timer so I think thats the problem. However I have been able to cause the same problem with JavaNoob's code by changing the screen resolution from 16 bit to 32 bit color. Any ideas on how to fix this?

[caraiz]

I had the same problem, and it happened because i changed to fullscreen mode with 16 bits and my desktop was at 32 bits.... Try change to fullscreen using the actual desktop deep color

1	device.getDisplayMode().getBitDepth()

[Kommi]

Ok I got it fixed. It was my rnedering code and it does not happen anymore.

Games published by our own members! Check 'em out!

[Abuse]

thats a JVM crash though, it shouldn't happen under *any* circumstances

I wouldn't bother reporting it though, fullscreen is still packed full of bugs, even in 1.4.2  

[Kommi]

actually I dont know exactly what I did. I had two rectangles which were objects responsible for painting themselves flying around. I lost the original class file for these objects which I wrote a while ago so I wrote a quick an dirty one. Since I have learned a lot more I wrote it to the best of my current abilitis in Java. And I no longer get the white screen or the crashes. (althought it still happened like once). I dont think that an me reinstalling the jvm and the sdk is what improved it.