Welcome to yEd Q&A!
Here you can ask questions and receive answers from other members of the community and yEd developers. And you can tell us your most wanted feature requests.


Error message "IllegalStateException: Buffers have not been created"

+1 vote
This error seems to be a problem of the Java platform on Windows and cannot be fixed in yEd. Since we were not able to reproduce this error, we're interested in hearing about its effects.

If you encountered this error, please add a comment below and tell us whether yEd worked normally after the error message appeared.
in Help by [yWorks] (26.8k points)
Maybe here is a clue how to reproduce the bug:
I've three displays attached to a Windows 7/64bit machine, two are attached via DVI to an nVidia graphics, one is attached via HDMI on an Intel GPU built in the Core i5 CPU.
I can start yEd on nVidia1 and move it on nVidia2 and maximize it or change its size - all without issues. But as soon as I move the window to Intel1 and try to resize it or maximize it, I get the error.
yEd does not work after the error, it just repeats over and over until I say Quit. Should you need more assistance reproducing the bug, I'd be glad to help.
I have the same experience as stated in the previous comment. yEd doesn't work normally after the error message. you have to close the program first.

How to reliable reproduce the bug if you have two monitors (maybe two graphic cards are required):
1. Start the program.
2. Move it to the other monitor.
3. Perform a resize of the program window (maximize or change the size with the mouse).

There seems to be a difference when you change the primary monitor.
When my primary monitor is the external monitor and I move the program to the notebook display I get an error message.
If my primary monitor ist the notebook display and I move the program to the external monitor the program just freezes and I get no error message at all.

My System:
Notebook Lenovo Thinkpad T520
Graphics card 1: Intel HD Graphics 3000
Graphics card 2: NVIDIA NVS 4200M
Windows 7 Professional (x64)
Addition to my above comment:
It seems you need 2 graphic cards. With a notebook with only one graphics card (Nvidia 3100 something) a colleague of mine couldn't reproduce the bug.
Thank you very much for the additional information.
I have the very same problem when I resize the yed-window (lenovo x420s dual-graphic card, win7 pro x64, java 1.7.09).
I got this bug on a laptop with i7 processor (build in gfx chip) and dedicated graphics chip.

I started the program. Clicked new document. Moved it to monitor #2. And the error popped up.
Another way to trigger the error is if using a laptop in a docking station with attached external monitor (not mirroring, extended desktop display mode). Removing the laptop from the dock will trigger the error right away.
Only option is to close yEd and loose any not saved changes (confirming with ok is endless loop of error messages).
My System is the same setup as already reported by another user:
Notebook Lenovo Thinkpad T520
Graphics card 1: Intel HD Graphics 3000
Graphics card 2: NVIDIA NVS 4200M
Windows 7 Professional (x64)
I was able to reproduce this by remote desktopping into a computer already running yEd. That is, start it up on my desktop (with two monitors, as it happened), then remote desktop into it. This caused the error every time. It also wouldn't dismiss - upon hitting OK it immediately recreated the window. Had to close.
This was my case too, but I don't know if it is reproducible. Anyway, Yed was not able to continue and had to by closed (by dialog). As the data were saved, no problem.

WinXP sp3 32 bit

java.lang.IllegalStateException: Buffers have not been created
    at sun.awt.windows.WComponentPeer.getBackBuffer(Unknown Source)
    at java.awt.Component$FlipBufferStrategy.getBackBuffer(Unknown Source)
    at java.awt.Component$FlipBufferStrategy.updateInternalBuffers(Unknown Source)
    at java.awt.Component$FlipBufferStrategy.revalidate(Unknown Source)
    at java.awt.Component$FlipBufferStrategy.revalidate(Unknown Source)
    at java.awt.Component$FlipBufferStrategy.getDrawGraphics(Unknown Source)
    at javax.swing.BufferStrategyPaintManager.prepare(Unknown Source)
    at javax.swing.BufferStrategyPaintManager.paint(Unknown Source)
    at javax.swing.RepaintManager.paint(Unknown Source)
    at javax.swing.JComponent.paint(Unknown Source)
    at java.awt.GraphicsCallback$PaintCallback.run(Unknown Source)
    at sun.awt.SunGraphicsCallback.runOneComponent(Unknown Source)
    at sun.awt.SunGraphicsCallback.runComponents(Unknown Source)
    at java.awt.Container.paint(Unknown Source)
    at java.awt.Window.paint(Unknown Source)
    at javax.swing.RepaintManager.paintDirtyRegions(Unknown Source)
    at javax.swing.RepaintManager.paintDirtyRegions(Unknown Source)
    at javax.swing.RepaintManager.prePaintDirtyRegions(Unknown Source)
    at javax.swing.RepaintManager.access$700(Unknown Source)
    at javax.swing.RepaintManager$ProcessingRunnable.run(Unknown Source)
    at java.awt.event.InvocationEvent.dispatch(Unknown Source)
    at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
    at java.awt.EventQueue.access$200(Unknown Source)
    at java.awt.EventQueue$3.run(Unknown Source)
    at java.awt.EventQueue$3.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
    at java.awt.EventQueue.dispatchEvent(Unknown Source)
    at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
    at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
    at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
    at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
    at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
    at java.awt.EventDispatchThread.run(Unknown Source)

3 Answers

0 votes
Yes. It worked just fine when I restarted it. (win7 64 bit)
0 votes
I have 2 monitors attached to a Win7 Pro x64. I had 3 diagrams open in yEd 3.10.1 running on Java HotSpot Client VM 1.7.0_09. I connected to the machine using remote desktop and could use yEd without a hitch. I disconnected RDP without logging off and found the error message the next day on the console. Pressing OK on the error dialog pointing to this page did not help, the dialog was immediately reshown. Restarting the application helped, everything worked just fine.
0 votes
have the same error message My Environment: Windows: 7 Java Version: 1.7.0_09 Yed Version: 3.10.1 Notebook with two graphic cards, NVidia and Intel graphic onboard After pressing 'OK',the error message displays immediatly again. Can't do anything with the yed window until i close yed. My Notebook is connected with an external display via hdmi. The main desktop (primary screen with the taskbar) is on the external display while the enhanced desktop (secondary screen) is on the Notebooks display. This is what I've done when the error occured: Yed was not started, so I just double clicked the .graphml file. Yed was automatically started maximized on the enhanced desktop (secondary screen)(on the Notebooks display). After closing yed and double clicking the .graphml file a second time, yed came up on the main desktop (primary screen). This time it was not maximized and no error occured. I moved the window then back to the enhanced desktop (Notebook display) and maximized it manually. Bam... the error occured again. I can maximize it on the primary screen without problems. So I switched the primary screen to the notebooks display and enhanced the desktop to the external display. As long as yed is just maximized on the primary screen everything is fine, after moving the window to the enhanced desktop and maximizing it the window freezed. No error message, the window just does'nt respond anymore.
Thank you very much for the additional information.

Please note, though, that the current version of yEd (3.14.1 at the time of this writing), uses a much newer Java runtime environment which severely reduces the likelihood of triggering the "Buffers have not been created" problem.

In short, please try out the current version of yEd. ;-)
Legal Disclosure | Privacy Policy