Opened 12 years ago
Last modified 3 years ago
#8761 closed bug
Software renderer should gracefully handle unsupported color spaces. — at Version 3
| Reported by: | xray7224 | Owned by: | kallisti5 |
|---|---|---|---|
| Priority: | normal | Milestone: | R1/beta4 |
| Component: | Kits/OpenGL Kit | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description (last modified by )
Currently, if one attempts to instantiate the mesa software renderer (legacy or new) in an unsupported color space (i.e. if the desktop is set to 8-bit color), the app will crash into the debugger. This should be handled a bit more gracefully. Simply removing the debugger() call doesn't appear to suffice though, since the return from _SetupRenderBuffer() is ignored, causing issues elsewhere later.
Change History (3)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
I was yes, sorry. I don't know why it defaults to that. It works fine now i've switched it to 32 bit mode.
comment:3 by , 12 years ago
| Description: | modified (diff) |
|---|---|
| Owner: | changed from to |
| Status: | new → assigned |
| Summary: | OpenGL Kits crashing. → Software renderer should gracefully handle unsupported color spaces. |
No problem, it should fail gracefully in that case instead of simply hitting the debugger though.
Note:
See TracTickets
for help on using tickets.
Are you running in 8-bit color mode? If so, that's not currently supported.