[Solved] After the monitor exits the standby mode, the browser page freezes

[sgunhouse]

sgunhouse Moderator Volunteer @Guest last edited by

@digital86 Is this the same as all those posts about Opera not working after the computer leaves sleep mode, or have you found a way to get the monitor in standby mode without the computer sleeping?

[A Former User]

A Former User @sgunhouse last edited by

@sgunhouse My computer works constantly, without going into hibernation and sleep. Only the monitor turns off after 1 minute of inactivity. Here is a screenshot of the power management settings.

[A Former User]

A Former User last edited by

I forgot to say, in the Chrome browser, everything is the same. But the Pale Moon browser and Mozilla work without freezing.

[leocg]

leocg Moderator Volunteer @Guest last edited by

@digital86 Probably a Chromium issue then. Any difference if you disable hardware acceleration.

[A Former User]

A Former User @leocg last edited by

@leocg I tried disabling hardware acceleration, but it didn't help.

[A Former User]

A Former User last edited by

I am also interested in whether this error occurs only for me, or for many people?

[leocg]

leocg Moderator Volunteer @Guest last edited by

@digital86 Don't remember have seen it happening here.

[sgunhouse]

sgunhouse Moderator Volunteer @Guest last edited by

@digital86 I couldn't say many people configure their computer that way. So I wouldn't be surprised if this is the same as the sleep issue, just no one knew it wasn't really the sleep which caused it.

[A Former User]

A Former User @sgunhouse last edited by

@sgunhouse I read earlier problems with the Opera browser, after waking up from sleep. In most cases, the browser just slows down, or freezes for unknown reasons. And working in such a browser becomes very unpleasant. Only restarting the PC helps. I do not have anything like this and everything works well after right-clicking. Therefore, I think my case is not like the others.

[A Former User]

A Former User last edited by

Hey, guys. The problem disappeared by itself. It may have been fixed in the last update.