Opera GX creates "debug.log" whenever it opens a PDF file
-
Cynthia7979 last edited by Cynthia7979
Operating System: Windows 10 Home
Opera Version: LVL 5 (core: 101.0.4843.55)Description:
Starting around this week, OperaGX began creating a new, visible text filedebug.log
whenever it was used to open a PDF file. The content of the file suggests that it is the result of the browser's Chromium core producing a warning message. It is always created under the same path that the PDF is in, and will be created unless there isn't sufficient permission.The image below shows the file (left) after opening a PDF (right):
The content within one of those files:
[0831/224114.810:ERROR:check.cc(290)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
I suspect it coming from the Chromium core because this line can be found in Chromium's source code (check.cc):
void NotReachedError::TriggerNotReached() { // This triggers a NOTREACHED() error as the returned NotReachedError goes out // of scope. NotReached() << "NOTREACHED log messages are omitted in official builds. Sorry!"; }
This isn't a serious problem or anything, but it is weird that it just began showing up recently. Hopefully it's going to be an easy fix for the devs!
Steps to Reproduce:
- Create a PDF file in a directory where Opera GX has permissions to read from and write to
- Double-click the file to open it (typing file link in Opera GX will not reproduce the issue)
- Navigate back to the folder where the PDF file is in. A new
debug.log
file should have been created with one line in it.
Note that reloading the PDF in Opera GX will also not create or update
debug.log
. Ifdebug.log
already exists in the right directory when opening a PDF, an additional line will be appended to it.Expected Behavior: No
debug.log
file should be created, or at least visible to the user.
Edit: Issue persists in LVL 5 (core: 101.0.4843.81)
-
docentyt last edited by
Same problem on LVL 5 (core: 102.0.4880.55). Please fix this. It is really annoying.
-
george2014 last edited by george2014
debug.log also generated after automatic update check in opera task scheduler, there's no solution to stop this, you can delete task scheduler, but sometimes debug.log reapear in opera folder with same message, new chromium + maybe webview also causes this logs to reapear, it started around few months ago, i found this logs in many folders, but main folder is operagx, sometimes desktop+utorrent folder, or documents, so this is common problem probably, it always says same thing in the log:
Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry! probably it is fixable