stdout flooded with "insertMessage(183): GL start/end of group: NOTIFICATION: ..."
Categories
(Core :: Graphics, defect)
Tracking
()
People
(Reporter: mozbugz, Unassigned)
Details
When running my local Windows builds, I get tens-hundreds of thousands of messages like these:
INFO: insertMessage(183): GL start of group: NOTIFICATION: TextRun
INFO: insertMessage(183): GL end of group: NOTIFICATION: TextRun
INFO: insertMessage(183): GL start of group: NOTIFICATION: B_Image
INFO: insertMessage(183): GL end of group: NOTIFICATION: B_Image
INFO: insertMessage(183): GL end of group: NOTIFICATION: alpha batches
INFO: insertMessage(183): GL end of group: NOTIFICATION: picture cache target
It doesn't seem reasonable or valuable to output this many messages!
This makes it very difficult to see my own logging.
It'd be great if this output could be moved to a MOZ_LOG (or similar), so it's off by default.
It seems to come from https://searchfox.org/mozilla-central/rev/8d722de75886d6bffc116772a1db8854e34ee6a7/gfx/angle/checkout/src/libANGLE/Debug.cpp#158
Workaround: I can put an early return;
there locally, when I need to silence them in order to do my own work.
Note: I run MOZ_DISABLE_CONTENT_SANDBOX=1 ./mach run "$@" 2>&1 | tee
, otherwise I don't see my own debugging output; but without it I also don't see all those "GL" messages, which may be why nobody complained before?
It's a bit scary to think that there's all this work done to output millions of messages into the void! 😛
Comment 1•4 years ago
|
||
This should be using Angle's logging system, which I'm pretty sure should not be logging INFOs to stdout by default. They definitely don't get output on my computer. Can I see your .mozconfig
and your env
output to see if anything could be setting the log level incorrectly?
Reporter | ||
Comment 2•4 years ago
|
||
Thank you for looking into this.
Did you try with MOZ_DISABLE_CONTENT_SANDBOX=1 ./mach run 2>&1 | tee
? And that was on Windows 10.
mozconfig:
ac_add_options --enable-debug
ac_add_options --enable-debug-symbols
ac_add_options --enable-optimize
ac_add_options --enable-warnings-as-errors
ac_add_options --disable-crashreporter
I'll DM you my env
...
Comment 3•4 years ago
|
||
I can't see anything in there that seems like it would cause this. Yes, I'm on windows 10 and used that exact command line.
Jeff, do you anything about Angle's logging framework, and why it'd be logging everything here?
Comment 4•4 years ago
|
||
This looks like it's debug-only.
It looks like ANGLE is just very log-happy.
It would take changes to ANGLE itself to quiet this down.
For now I think grep -v
will be your friend. :(
Description
•