Hello Guest

Please add suggested workaround for VM bug 6539705

  • 8 Replies
  • 5212 Views
Please add suggested workaround for VM bug 6539705
« on: December 05, 2010, 23:45:30 »
I'm getting several reports of users hitting this VM bug: http://bugs.sun.com/view_bug.do?bug_id=6539705

Unfortunately the recommended workaround - explicitly calling loadLibrary("awt"), or Toolkit.getDefaultToolkit() - doesn't work as someone has already noted. Would one of you guys be able to put the jni workaround (in the last comment) directly into LWJGL?

Thanks.
« Last Edit: December 05, 2010, 23:47:53 by Orangy Tang »

*

Offline Matzon

  • *****
  • 2242
Re: Please add suggested workaround for VM bug 6539705
« Reply #1 on: December 06, 2010, 06:29:18 »
hmm, afaik we dont need this because we're explicitelt using the /delayload option when linking

Re: Please add suggested workaround for VM bug 6539705
« Reply #2 on: December 06, 2010, 11:11:12 »
Well that's very odd then, because I'm definitely getting reports which look *exactly* like that bug. :(

*

Offline Matzon

  • *****
  • 2242
Re: Please add suggested workaround for VM bug 6539705
« Reply #3 on: December 06, 2010, 11:23:02 »
can you possibly test on older versions ? - thinking that the CI may be interfering?

Re: Please add suggested workaround for VM bug 6539705
« Reply #4 on: December 06, 2010, 11:51:53 »
can you possibly test on older versions ? - thinking that the CI may be interfering?
I can do a special build for one of my affected users, but obviously I can't ask them to try loads of versions. Have you got a specific lwjgl version you'd like me to try?

Also, what's the CI?
« Last Edit: December 06, 2010, 11:53:39 by Orangy Tang »

*

Offline Matzon

  • *****
  • 2242
Re: Please add suggested workaround for VM bug 6539705
« Reply #5 on: December 06, 2010, 18:01:54 »
CI = Hudson

I was just thinking about trying an old verson 2.2 for instance?

*

Offline Matzon

  • *****
  • 2242
Re: Please add suggested workaround for VM bug 6539705
« Reply #6 on: December 07, 2010, 06:55:00 »
Quote
[12:24:35] <Diablo-D3> that thread that just popped up
[12:24:50] <Diablo-D3> isnt that the same one that happened on my app, and all I had to do was explicitly set DISPLAY=:0 to fix it?
[12:24:57] <Diablo-D3> (happens on headless opencl clients)

Re: Please add suggested workaround for VM bug 6539705
« Reply #7 on: December 07, 2010, 23:47:33 »
I may be being stupid, but what does DISPLAY:=0 mean in this context?

cool story, bro