Go Back   DisplayLink Forum > DisplayLink Graphics Technology > Mac Software
Register FAQ Calendar Today's Posts Search

 
 
Thread Tools Search this Thread Display Modes
Prev Previous Post   Next Post Next
Old 09-12-2011, 04:11 PM   #8
tenuki
Junior Member
 
Join Date: Jul 2011
Posts: 5
Default

I just have to say - npgall you have to be one of the most helpful individuals on the planet. I hope all that good karma comes crashing down on you soon!!

Quote:
Originally Posted by npgall View Post
Hi hotcha3,

Your log indicates where the app crashed, and I was able to reproduce the problem on my machine with this code:

import java.awt.*;
public class Temp {
public static void main(String[] args) {
for (GraphicsDevice graphicsDevice : GraphicsEnvironment.getLocalGraphicsEnvironment(). getScreenDevices()) {
System.out.println(graphicsDevice.getAvailableAcce leratedMemory());
}
}
}

...the code above cycles through the available graphics devices and queries each one for the amount of accelerated memory (presumably video memory) available.

On my machine I have three graphics devices, the built-in Intel one, and two DisplayLink USB cards. The JVM crashes when I call this method on either of the DisplayLink devices. But it works for the built-in one.

So this is a reproducible test case that could help DisplayLink to fix the issue in their drivers.

In the mean time, it might also be possible for Prorealtime to avoid calling this method. I'm using several Java apps, IntelliJ IDEA mostly, and I haven't encountered this issue, so presumably my apps just aren't using that method.

It's a method that a real-time graphics app like Prorealtime might well like to use of course, to improve graphics performance. But maybe they could make an update for you/others in this situation, such that under some circumstances or if a "system property" is set, they can avoid calling that method.

It's likely this is a bug in DisplayLink drivers. There's also a chance that this problem could be caused by a bug in Apple's Java or an underlying system. A bug in DisplayLink drivers does sound more likely though.

Over to DisplayLink I guess...
tenuki is offline   Reply With Quote
 

Tags
lion java bug


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 04:15 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2026, vBulletin Solutions, Inc.