Search Issue Tracker
Not Reproducible
Votes
32
Found in
5.4.0b22
Issue ID
805222
Regression
Yes
SUCCEEDED(hr) error message after editor regains focus
1. open succeded scene
2. expend canvas and select button
3. hit the color widget in image script to change its color
4. hit the color picker button
5. select a color anywhere
6. close color picker
7. hit anywhere in wondows away from unity
8. re-click scene view
9. redo steps 4 to 8.
result: SUCCEEDED(hr)
rc.right == m_GfxWindow->GetWidth() && rc.bottom == m_GfxWindow->GetHeight()
Found in 5.4.b22
Comments (44)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
lassade
Oct 13, 2016 18:01
Same problem with 5.4.1f1. Here i used the color picker and ever thing was fine, but when i changed to my web browser (chrome) and bak to unity the messages appeared.
MuHaGames_Avee
Oct 13, 2016 14:02
I got it too, my best guess is that the problem is caused by having more than one monitor, each with a different resolution (1920x1080 and 2560x1440 in my case). Can anyone confirm or deny this? I'm thinking about buying a QHD monitor to replace the HD one, but I would be pretty annoyed if this didn't help.
hwizard
Oct 03, 2016 18:33
Same here 5.4.1f1
bpdavis2006
Sep 10, 2016 22:41
If nothing else, could you at least comment out the calls to Debug.LogError("SUCCEDED(hr)") That alone quickly fills up the console log.
Loden_Heathen
Sep 04, 2016 15:06
We get this on 5.4.0 release build, we have gotten this from Unity 4 on up to today and you can find various similar bugs in the issue tracker usually closed as unable to reproduce or similar.
Typically we just accept this is a nature of the editor and work on through it; however this has become quite frequent in some cases such as when messing with lighting settings it starts spewing thousands of messages to the log and will eat a growing amount of ram till we kill or it dies on its own.
We have reported several crash bugs and have noted this message in the logs not sure if its related or not though as Unity doesn't always or only crash when this message is thrown.
We most frequently get the message when working with lighting especially if you manually bake then cancel the bake.
SeriousACZ
Sep 04, 2016 05:40
Ditto - 5.4.0f3
cinas
Aug 27, 2016 19:56
Get this issue sometime as well... is there anything harmful about it?
TruffelsAndOranges
Aug 19, 2016 10:37
Same problem. Unity 5.4.0f3.
infered5
Aug 05, 2016 08:17
Happens in fresh install, 0 assets, 0 code, usually when exiting playmode. Windows 10, happens in both 64 and 32 bit versions of Unity Editor.
Ebon-Drake
Aug 04, 2016 18:32
I have the same issue when I add UI to a scene. I have a text as well as two buttons.