CNN videos hang / get stuck after a few seconds on HWA = "on"
-
thartneid last edited by
There has been some discussion about the HWA-setting (Hardware acceleration) in this forum recently, mainly meant as a remedy for the v.46 problem of getting very sluggish upon loading data-rich sites, worst example of all being "Google maps" which will never load entirely and render the site unusable without the final navigational layers ever to come up - UNLESS "HWA" is set to "on".
Unfortunately it seems that this is no solution either because I have verified on several systems by now, that it is exactly this setting that will bring up a long-standing bug in Opera: CNN-videos (http://us.cnn.com) will hang / get stuck after a few seconds and never resume to be played in entirety as soon as HWA is set to "on".
Could you please verify this strange behavior as a general phenomenon also occurring on your systems - or not. And if so, please also verify if it goes away on "HWA" set to "off" - which unfortunately brings back all the endless-loading-troubles since v.46. (Until v.45 loading pages with "HWA"=off resulted in only minimal delay and therefore was an acceptable compromise, apart from the fact that up until v.45 videos on 4K-displays were not upscaled properly in "full-screen-mode" and played in native resolution in the upper left corner instead).
greetings
Tom
-
thartneid last edited by
Please specify if they played fine with HWA set to "on", too - or did they only in the "off"-position of that "switch"?
-
thartneid last edited by
Well, to demonstrate the difference of course - that is, if there is any, as I have seen on half a dozen of different systems which all happen to hang with CNN-videos, but only on HWA="on".
greetings
Tom
-
thartneid last edited by
Meanwhile v.46.0.2597.61 is out ...
and the calamities described in this thread go on unchanged.
Tom
-
thartneid last edited by
Sorry "leocg", I somehow do not get the meaning of your last question. Reported, yes. Fixed? Still waiting, all I'm saying. How could it be "not the case" to be a problem if it can be clearly reproduced, depending on the "HWA"-setting = "on" and not occurring on "HWA" = "off"? And why was "HWA" = "off" not a problem until v.45 and has become a massive problem with many other sites (not only "Google maps") only since v.46?
greetings
Tom
-
thartneid last edited by
Thanks "leocg", I wasn't aware of that bug reporting procedure. I went under the assumption that bugs are reported by discussing them in this forum. Meanwhile there is such a report: DNAWIZ-18404. Does that mean that the so far unfixed "Google-maps" / v.46-general-loadig-bug may not have been officially reported either while having been amply discussed in this forum?
Btw, did you Opera-forum guys notice that this very site has practically been down for a day and a half from thursday 7/27 to friday 7/28? In particular when logged in you couldn't get past the "overview"-page which again kept loading and loading with the busy-cursur blinking frantically (sounds familiar with Opera v.46 from "Google maps"?)?
As soon as one would proceed to the Windows- (or any) problems page the browser kept jumping back to the "overview"-page within seconds again. That one seems now fixed. I'm wondering though if that phenomenon might also have been related to the v.46-loading problem and so far couldn't figure out how to determine if that one, too, has been "officially" reported via the "wizard"? Because over there it is only mentioned that a bug already discussed in the forum will probably have been "officially" reported via the "wizard" in the first place - but how to be sure?
greetings
Tom
-
leocg Moderator Volunteer last edited by
Does that mean that the so far unfixed "Google-maps" / v.46-general-loadig-bug may not have been officially reported either while having been amply discussed in this forum?
There is a chance.
Btw, did you Opera-forum guys notice that this very site has practically been down for a day and a half from thursday 7/27 to friday 7/28?
There is a topic about it and the information is that the issue was already fixed.
