Exception on render thread: "NGTriangleMesh: buildGeometry failed"

[Kevin Rushforth]

Yes, so we might want to file a bug (we have several places in native 
where we should do a better job about handling native OOM).

-- Kevin


Jim Graham wrote:
> Would a better exception help?  OOME?
>
>             ...jim
>
> On 6/28/16 9:18 AM, Kevin Rushforth wrote:
>> Glad to hear it.
>>
>> -- Kevin
>>
>>
>> GUEVEL, Emanuel wrote:
>>> It worked.
>>>
>>> The problem is not present anymore after switching to a 64-bit JVM.
>>>
>>> Many thanks for this. :)
>>>
>>> Best regards,
>>> Emanuel
>>>
>>>
>>> -----Message d'origine-----
>>> De : Kevin Rushforth [mailto:kevin.rushforth at oracle.com] Envoyé : 
>>> mardi 28 juin 2016 16:33
>>> À : GUEVEL, Emanuel
>>> Cc : openjfx-dev at openjdk.java.net
>>> Objet : Re: Exception on render thread: "NGTriangleMesh: 
>>> buildGeometry failed"
>>>
>>> This suggests that you are running out of native memory. You might 
>>> consider using a 64-bit JVM.
>>>
>>> -- Kevin
>>>
>>>
>>> GUEVEL, Emanuel wrote:
>>>
>>>> Hello,
>>>>
>>>> I am using JavaFX 8 for a 3D visualization application.
>>>> I display a set of TriangleMesh and under some circumstances, an 
>>>> exception is thrown on the JavaFX rendering thread
>>>> ("QuantumRenderer") in NGTriangleMesh.validate().
>>>> The message is "NGTriangleMesh: buildGeometry failed".
>>>>
>>>> I know this exception is thrown when the mesh geometry data are 
>>>> incorrect, but in this case the behavior is
>>>> inconsistent : the same data may or may not be considered invalid.
>>>> It seems the problem occurs more often when more memory is 
>>>> allocated to the JVM (via -Xms and -Xms command arguments).
>>>>
>>>> I use JDK8u92 32 bits on Windows.
>>>>
>>>> Does anyone encounter the same problem ?
>>>> Do you have a solution ?
>>>>
>>>> Thanks in advance.
>>>>
>>>> Best regards,
>>>> Emanuel
>>>>
>>>> This message contains information that may be privileged or 
>>>> confidential and is the property of the Capgemini Group.
>>>> It is intended only for the person to whom it is addressed. If you 
>>>> are not the intended recipient, you are not
>>>> authorized to read, print, retain, copy, disseminate, distribute, 
>>>> or use this message or any part thereof. If you
>>>> receive this message in error, please notify the sender immediately 
>>>> and delete all copies of this message.
>>>>