-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
change system time backward will let st-srs behavior abnormal #3978
Labels
EnglishNative
This issue is conveyed exclusively in English.
Enhancement
Improvement or enhancement.
Comments
Nice work! Welcome to patch it. |
suzp1984
added a commit
to suzp1984/srs
that referenced
this issue
Mar 7, 2024
suzp1984
added a commit
to suzp1984/srs
that referenced
this issue
Mar 7, 2024
suzp1984
added a commit
to suzp1984/srs
that referenced
this issue
Mar 9, 2024
suzp1984
added a commit
to suzp1984/srs
that referenced
this issue
Mar 9, 2024
suzp1984
added a commit
to suzp1984/srs
that referenced
this issue
Mar 18, 2024
suzp1984
added a commit
to suzp1984/srs
that referenced
this issue
Mar 18, 2024
suzp1984
added a commit
to suzp1984/srs
that referenced
this issue
Mar 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
EnglishNative
This issue is conveyed exclusively in English.
Enhancement
Improvement or enhancement.
Root Cause
srs/trunk/3rdparty/st-srs/md.h
Lines 113 to 116 in fa8096a
the default implementation of get timestamp of microseconds is depends on system time.
man gettimeofday
the
st-srs
has api that let us to config our own get timestamp function, but srs didn't config it.srs/trunk/3rdparty/st-srs/sync.c
Lines 57 to 85 in fa8096a
Solutions
refactor
MD_GET_UTIME
or Config a time function based on more robust solutions, e.g. system uptime, the timestamp since the system boot.Version
All version
To Reproduce
Steps to reproduce the behavior:
make
./helloword
Hello
print will stuck.Expected behavior
Change the system time should not impact the st-srs behavior.
The text was updated successfully, but these errors were encountered: