Webm problem on Google Chrome

fabiojapa

fabiojapa

New Member
Last edited:
fabiojapa

fabiojapa

New Member
Yesterday(2020-12-09) I upgrade de WCS to latest version 5.2.856

The stream recording was working fine recording webm files, but today(2020-12-10) the problem reocurred.

A new example:

The logs:

2020-12-10T10:40:32.663-0300: 62479.384: [GC (Allocation Failure) 2020-12-10T10:40:32.663-0300: 62479.384: [ParNew: 17108K->141K(19008K), 0.0016481 secs] 52602K->35660K(70040K), 0.0017354 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
2020-12-10T10:40:32.866-0300: 62479.587: [GC (Allocation Failure) 2020-12-10T10:40:32.866-0300: 62479.587: [ParNew: 17037K->189K(19008K), 0.0017032 secs] 52556K->35718K(70040K), 0.0017969 secs] [Times: user=0.01 sys=0.00, real=0.00 secs]
2020-12-10T10:40:33.071-0300: 62479.791: [GC (Allocation Failure) 2020-12-10T10:40:33.071-0300: 62479.791: [ParNew: 17085K->223K(19008K), 0.0016526 secs] 52614K->35774K(70040K), 0.0017602 secs] [Times: user=0.00 sys=0.00, real=0.01 secs]
2020-12-10T10:40:33.146-0300: 62479.867: [GC (Allocation Failure) 2020-12-10T10:40:33.146-0300: 62479.867: [ParNew: 17119K->146K(19008K), 0.0016446 secs] 52670K->35721K(70040K), 0.0017322 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
2020-12-10T10:40:33.355-0300: 62480.076: [GC (Allocation Failure) 2020-12-10T10:40:33.355-0300: 62480.076: [ParNew: 17042K->198K(19008K), 0.0017126 secs] 52617K->35783K(70040K), 0.0018021 secs] [Times: user=0.01 sys=0.00, real=0.00 secs]
2020-12-10T10:40:33.555-0300: 62480.276: [GC (Allocation Failure) 2020-12-10T10:40:33.555-0300: 62480.276: [ParNew: 17094K->242K(19008K), 0.0016856 secs] 52679K->35849K(70040K), 0.0017759 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
2020-12-10T10:40:33.636-0300: 62480.356: [GC (Allocation Failure) 2020-12-10T10:40:33.636-0300: 62480.356: [ParNew: 17138K->202K(19008K), 0.0016243 secs] 52745K->35819K(70040K), 0.0017125 secs] [Times: user=0.01 sys=0.00, real=0.00 secs]
2020-12-10T10:40:33.837-0300: 62480.557: [GC (Allocation Failure) 2020-12-10T10:40:33.837-0300: 62480.557: [ParNew: 17098K->242K(19008K), 0.0026533 secs] 52715K->35884K(70040K), 0.0027474 secs] [Times: user=0.01 sys=0.00, real=0.00 secs]
2020-12-10T10:40:33.917-0300: 62480.637: [GC (Allocation Failure) 2020-12-10T10:40:33.917-0300: 62480.637: [ParNew: 17138K->167K(19008K), 0.0016048 secs] 52780K->35834K(70040K), 0.0016930 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
2020-12-10T10:40:34.121-0300: 62480.841: [GC (Allocation Failure) 2020-12-10T10:40:34.121-0300: 62480.841: [ParNew: 17063K->225K(19008K), 0.0030938 secs] 52730K->35902K(70040K), 0.0032070 secs] [Times: user=0.00 sys=0.00, real=0.01 secs]
2020-12-10T10:40:34.323-0300: 62481.044: [GC (Allocation Failure) 2020-12-10T10:40:34.323-0300: 62481.044: [ParNew: 17121K->263K(19008K), 0.0016681 secs] 52798K->35971K(70040K), 0.0017966 secs] [Times: user=0.01 sys=0.00, real=0.00 secs]
2020-12-10T10:40:34.411-0300: 62481.132: [GC (Allocation Failure) 2020-12-10T10:40:34.412-0300: 62481.132: [ParNew: 17159K->211K(19008K), 0.0017706 secs] 52867K->35947K(70040K), 0.0018607 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
2020-12-10T10:40:34.414-0300: 62481.134: [GC (CMS Initial Mark) [1 CMS-initial-mark: 35735K(51032K)] 36103K(70040K), 0.0013248 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
2020-12-10T10:40:34.415-0300: 62481.136: [CMS-concurrent-mark-start]
2020-12-10T10:40:34.588-0300: 62481.309: [CMS-concurrent-mark: 0.173/0.173 secs] [Times: user=0.32 sys=0.02, real=0.17 secs]
2020-12-10T10:40:34.588-0300: 62481.309: [CMS-concurrent-preclean-start]
2020-12-10T10:40:34.590-0300: 62481.310: [CMS-concurrent-preclean: 0.001/0.001 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
2020-12-10T10:40:34.590-0300: 62481.310: [CMS-concurrent-abortable-preclean-start]
2020-12-10T10:40:34.614-0300: 62481.335: [GC (Allocation Failure) 2020-12-10T10:40:34.614-0300: 62481.335: [ParNew: 17107K->187K(19008K), 0.0018212 secs] 52843K->35934K(70040K), 0.0019300 secs] [Times: user=0.01 sys=0.00, real=0.00 secs]
2020-12-10T10:40:34.814-0300: 62481.535: [GC (Allocation Failure) 2020-12-10T10:40:34.814-0300: 62481.535: [ParNew: 17083K->189K(19008K), 0.0017474 secs] 52830K->35965K(70040K), 0.0018407 secs] [Times: user=0.01 sys=0.00, real=0.00 secs]
2020-12-10T10:40:34.816-0300: 62481.537: [CMS-concurrent-abortable-preclean: 0.004/0.227 secs] [Times: user=0.45 sys=0.01, real=0.23 secs]
2020-12-10T10:40:34.819-0300: 62481.540: [GC (CMS Final Remark) [YG occupancy: 352 K (19008 K)]2020-12-10T10:40:34.819-0300: 62481.540: [Rescan (parallel) , 0.0011457 secs]2020-12-10T10:40:34.820-0300: 62481.541: [weak refs processing, 0.0001227 secs]2020-12-10T10:40:34.820-0300: 62481.541: [class unloading, 0.0107562 secs]2020-12-10T10:40:34.831-0300: 62481.552: [scrub symbol table, 0.0065031 secs]2020-12-10T10:40:34.838-0300: 62481.558: [scrub string table, 0.0007568 secs][1 CMS-remark: 35776K(51032K)] 36128K(70040K), 0.0194513 secs] [Times: user=0.02 sys=0.00, real=0.02 secs]
2020-12-10T10:40:34.839-0300: 62481.559: [CMS-concurrent-sweep-start]
2020-12-10T10:40:34.855-0300: 62481.575: [CMS-concurrent-sweep: 0.016/0.016 secs] [Times: user=0.03 sys=0.00, real=0.02 secs]
2020-12-10T10:40:34.855-0300: 62481.575: [CMS-concurrent-reset-start]
2020-12-10T10:40:34.857-0300: 62481.577: [CMS-concurrent-reset: 0.002/0.002 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
2020-12-10T10:40:34.918-0300: 62481.639: [GC (Allocation Failure) 2020-12-10T10:40:34.918-0300: 62481.639: [ParNew: 17085K->102K(19008K), 0.1271194 secs] 40469K->23495K(70040K), 0.1272309 secs] [Times: user=0.25 sys=0.00, real=0.13 secs]
2020-12-10T10:40:35.103-0300: 62481.824: [GC (Allocation Failure) 2020-12-10T10:40:35.103-0300: 62481.824: [ParNew: 16998K->115K(19008K), 0.0016799 secs] 40391K->23535K(70040K), 0.0017694 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
2020-12-10T10:40:35.301-0300: 62482.021: [GC (Allocation Failure) 2020-12-10T10:40:35.301-0300: 62482.021: [ParNew: 17011K->36K(19008K), 0.0016212 secs] 40431K->23486K(70040K), 0.0017128 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
2020-12-10T10:40:35.373-0300: 62482.094: [GC (Allocation Failure) 2020-12-10T10:40:35.373-0300: 62482.094: [ParNew: 16932K->16K(19008K), 0.0016502 secs] 40382K->23486K(70040K), 0.0017399 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
2020-12-10T10:40:35.571-0300: 62482.291: [GC (Allocation Failure) 2020-12-10T10:40:35.571-0300: 62482.291: [ParNew: 16912K->4K(19008K), 0.0015794 secs] 40382K->23474K(70040K), 0.0016728 secs] [Times: user=0.00 sys=0.00, real=0.01 secs]
2020-12-10T10:40:35.642-0300: 62482.362: [GC (Allocation Failure) 2020-12-10T10:40:35.642-0300: 62482.362: [ParNew: 16900K->4K(19008K), 0.0015936 secs] 40370K->23473K(70040K), 0.0016854 secs] [Times: user=0.01 sys=0.00, real=0.01 secs]
2020-12-10T10:40:35.840-0300: 62482.561: [GC (Allocation Failure) 2020-12-10T10:40:35.840-0300: 62482.561: [ParNew: 16900K->4K(19008K), 0.0014941 secs] 40369K->23473K(70040K), 0.0015857 secs] [Times: user=0.01 sys=0.00, real=0.00 secs]
2020-12-10T10:40:35.913-0300: 62482.633: [GC (Allocation Failure) 2020-12-10T10:40:35.913-0300: 62482.633: [ParNew: 16900K->4K(19008K), 0.0015220 secs] 40369K->23475K(70040K), 0.0016177 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
2020-12-10T10:40:36.114-0300: 62482.834: [GC (Allocation Failure) 2020-12-10T10:40:36.114-0300: 62482.834: [ParNew: 16900K->4K(19008K), 0.0015428 secs] 40371K->23475K(70040K), 0.0016367 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
2020-12-10T10:40:36.311-0300: 62483.032: [GC (Allocation Failure) 2020-12-10T10:40:36.311-0300: 62483.032: [ParNew: 16900K->4K(19008K), 0.0014766 secs] 40371K->23475K(70040K), 0.0015683 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
 
Last edited:
Max

Max

Administrator
Staff member
Hello!
We tested the recording on your server.
Keyframes do not appear regularly during publication, so the browser cannot then play back a recording.

To force keyframes to be sent, please add the following setting to the flashphoner.properties file:
Code: 
periodic_fir_request =true
Also, if your case involves working with stream records, we recommend enabling TCP transport:
Code: 
ice_tcp_transport =true
After the settings, you need to restart WCS using the command:
Code: 
systemctl restart webcallserver
 
Last edited:
Max

Max

Administrator
Staff member
fabiojapa said:
But the problem persists:

https://rec.igree.co/client/records/stream-b6b759b0-3bb9-11eb-b4e9-814719c9767d-nviucha9uvqpjtomfrgc6surhp.webm https://rec.igree.co/client/records/stream-d226dc10-3bba-11eb-b4e9-814719c9767d-90faqg4bvno4glgklspefmnlen.webm
Click to expand...
Unfortunately, your recordings are no longer available on the server.

Re-tested the recording function on your server. In the standard “Stream Recording” example, the recording problem does not appear. Tested in Chrome browser on desktop and mobile android.

1607916420798.png

1607916548429.png


Please specify how you test?

What device are you publishing the stream from? What channel (Mobile network, Wi-Fi, etc.)? Which browser are you using, which version?

Does the standard Stream Recording example show the problem?
 
Max

Max

Administrator
Staff member
We checked the recording work with Google Chrome version 86.0.4240.75 (official version) 64 bits.
When accessing the site by domain name, the problem is reproduced.

Previously, we tested on the current Google Chrome Version 87.0.4280.88 (Official Build) (64-bit) and accessed WCS directly (https://WCS.IP.address:8444). At the same time, 10 out of 10 tests were completed successfully.

Therefore, we recommend that you check your web server settings and update Google Chrome to the latest version.
 
fabiojapa

fabiojapa

New Member
The problem occurs with any version of Google Chrome.

As I said, the problem is intermittent. You already simulated the problem, when you started to attend this thread, right?

The stream recording works fine for hours, but for some unknown reason the problem start to occur for hours. If I restart the WCS, the stream record works fine again.
 
Max

Max

Administrator
Staff member
During testing on your server, we noticed that over time, at rest, the JVM begins to consume processor power (according to the top program, ~ 190%, i.e. two cores out of four are fully occupied).
The increased consumption of processing power can lead to recording problems. This issue is specific to Java 11 and recent builds of Java 8. Therefore, we recommend installing JDK12, which does not have such problems.

The installation process is described in detail in the documentation
https://docs.flashphoner.com/displa...rementsandprerequisites-ManualJDKinstallation

After installing JDK 12, remove the lines from the wcs-core.properties file
Code: 
-XX:+PrintGCDateStamps
-XX:+PrintGCDetails
And test the recording with new settings.
If not difficult, please report on the result.
 
fabiojapa

fabiojapa

New Member
Hello!

After the upgrade to JDK 12, the issue was resolved. We are still testing and it is working fine.

If the problem happens again, I will notice you in this thread.

Thank you!
 
Max

Max

Administrator
Staff member
Good day.
We fixed webm recordings playback issue in WCS build 5.2.906. This issue was not caused by JDK version.
 
You must log in or register to reply here.
Top