| Summary: | sdl initializes too long -> loading bmp doesnt work (?) | ||
|---|---|---|---|
| Product: | SDL | Reporter: | PJ <winhelp> |
| Component: | *don't know* | Assignee: | Ryan C. Gordon <icculus> |
| Status: | RESOLVED WONTFIX | QA Contact: | Sam Lantinga <slouken> |
| Severity: | minor | ||
| Priority: | P2 | ||
| Version: | 1.2.14 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Attachments: |
small image
Test program based on the pastebin example. |
||
|
Description
PJ
2011-05-23 09:40:16 UTC
Thanks for the report. Please let me know if you have a patch for this issue! Created attachment 748 [details]
Test program based on the pastebin example.
Just looked at this, and it _does_ fail to render, as reported...rather, it rendered just the top corner of the image on my computer.
However, if you pump the event queue, it renders the rest of it. See attached program that adds an event loop after the two-second delay. You'll see the image render after the delay is done.
So, strictly speaking, this _might_ be an X11-specific SDL bug, but I'm inclined to say it's not worth fixing, as any reasonable program will have an event loop.
Running it under valgrind without the event loop causes the bug to go away, too...race condition with the X server?
My guess as to the issue is that we have pending X11 data that hasn't been XFlush()'d, so running the even loop later pushes that data down the pipe. A bigger image will force a flush sooner, avoiding this problem. Or something. I'm not sure.
I think this is appropriate to leave as WONTFIX. It should only happen in small test programs like this.
--ryan.
|