Opened 2 years ago

Last modified 18 months ago

#10998 reopened enhancement

Removing the memory address in output messages' header?

Reported by: MasterQuestionable Owned by:
Priority: normal Component: avutil
Version: git-master Keywords: av_log debug
Cc: MasterQuestionable Blocked By:
Blocking: Reproduced by developer: no
Analyzed by developer: yes

Description

͏    Which is unhelpful for most cases. (primarily unnecessary verbosity, and diff noise)
͏    In particular for helpless users spamming "debug" output looking for help... mostly useless.

͏    For reference:
͏    ​https://github.com/MasterInQuestion/attach/commit/e18e5cd26b9d27bacefa685ba70d0d41bc7d7cbc
͏    ​https://trac.ffmpeg.org/attachment/ticket/10997/test.h265.txt#L32

͏    In rare cases shall it be needed: add ͏"-debug_mem"?

Change History (7)

comment:1 by MasterQuestionable, 2 years ago

comment:2 by MasterQuestionable, 2 years ago

͏    2 woe examples:
͏    ​https://trac.ffmpeg.org/ticket/11185
͏    ​https://trac.ffmpeg.org/ticket/11182#comment:32 [!]

͏    Woes even more...
͏    ​https://trac.ffmpeg.org/ticket/11464#comment:3 [!]
͏    ​https://trac.ffmpeg.org/ticket/11542#comment:description [!]
͏    ​https://trac.ffmpeg.org/ticket/11021#comment:description
͏    ​https://trac.ffmpeg.org/ticket/11110#comment:description
͏    ​https://trac.ffmpeg.org/ticket/11369#ticket [!]
͏    ​https://trac.ffmpeg.org/ticket/11368#comment:3 [!]
[!] Command output woefully meddled by TracWiki.

͏    There are always people tossing such unfiltered log alike:
͏    ​https://trac.ffmpeg.org/ticket/11478
͏    (primary point is that, the entire log is mostly irrelevant: mere verbiage)

Last edited 18 months ago by MasterQuestionable (previous) (diff)

comment:3 by Leo Izen, 20 months ago

Resolution: → invalid
Status: new → closed

comment:4 by MasterQuestionable, 20 months ago

Analyzed by developer: set
Resolution: invalid
Status: closed → reopened

͏    The described problem is perfectly valid.
͏    For nearly all cases I don't need the memory address.

͏    Even outright dropping the memory address output maybe acceptable for me.

͏    ----

͏    Read the full context, I must suggest.
͏    And I'm not interested in the revert war.

Last edited 20 months ago by MasterQuestionable (previous) (diff)

comment:5 by Leo Izen, 20 months ago

Resolution: → invalid
Status: reopened → closed

It's very helpful when posting a debug log for an issue. You may not personally care about it but it's helpful for developers.

comment:6 by MasterQuestionable, 20 months ago

Resolution: invalid
Status: closed → reopened

͏    Specifically, it's about the transient memory addresses mostly wouldn't be used.
͏    (in particular that from a different device passé)
͏    Piling-up garbage-like like in comment:2 etc.

comment:7 by Gyan, 20 months ago

There's certainly a case for a loglevel flag to disable or abbreviate it. For almost all CLI users asking for help, it's just bloat.

Last edited 20 months ago by Gyan (previous) (diff)
Note: See TracTickets for help on using tickets.