Eclipse Crashes With Bad Alloc Jvm Error

I just started having this problem today. I am using suse 10.3 with eclipse 3.2.2. I installed the latest security updates for suse this morning and now when I go to run eclipse I get the following error:

JVM terminated. Exit code=1
/usr/bin/java
-Xms40m
-Xmx256m
-jar /home/bpsnell/eclipse/./startup.jar
-os linux
-ws gtk
-arch x86
-launcher /home/bpsnell/eclipse/./eclipse
-name Eclipse
-showsplash 600
-exitdata 1e0003
-vm /usr/bin/java
-vmargs
-Xms40m
-Xmx256m
-jar /home/bpsnell/eclipse/./startup.jar

The console error message is as follows:

The program 'Eclipse' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 449 error_code 11 request_code 143 minor_code 5)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)

After some searching on the web (at the Ubuntu forums), it seems that the xorg update that occured today is causing this problem. Ubuntu has released a patch, but it does not appear that there is one for suse as yet. My question is, does anyone know a possible fix for this other than waiting for the update from suse? I use eclipse for a lot of my work, and I need it to work. Any help would be appreciated. Thanks

Look at this thread:

http://www.suseforums.net/index.php?showtopic=44755&hl=

-docarockus