View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0014535 | MMW v4 | DLNA/UPnP | public | 2017-11-11 03:30 | 2018-01-26 01:05 |
| Reporter | peke | Assigned To | |||
| Priority | urgent | Severity | block | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 4.1 | ||||
| Target Version | 4.1.20 | Fixed in Version | 4.1.20 | ||
| Summary | 0014535: DLNA: If DLNA server is accessed on close MMW throw background task warning | ||||
| Description | If UPnP/DLNA/Sync is accessed on close MMW throw background task warning that is confusing and do not let user know which process is actually interfere with closing. We should introduce Dialog with timeout (for system shutdown/restart) like: "UPnP/DLNA Service is being accessed by xy Device(s). Are you sure that you would like to quit and terminate background processes? [] Do not ask again [YES (10)][NO]" | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1860 | ||||
|
|
Based on the log the background task warning appeared while MM was casting to a DLNA renderer and was asking transport status repeatedly each second, MM should stop the requests on app close (which will also supress the warning and results in graceful app closing). Fixed in 4.1.20.1860 |
|
|
Ok, what about Warning dialog if you access MMW from DLNA device and you try to close MMW? I still think that there should be a warning like windows warns there are computers logged on shares and they will be terminated? |
|
|
I don't think that a warning is needed on the server side, such a warnings are mostly on the client side. If we want to introduce warning when MMW server is going to stop then we would need to show such a warning on each MMW close (supposing MMW was not installed as service), because we can never know how much of the content is already cached by clients and whether they are going to use any further content. In addition some clients (like LG TV) automatically scans content of whole MMW server after each start so I guess that such a warning would be rather annoying (with a need for '[x] Don't show this again' checkbox as you noted). Note that based on the user log MMW wasn't used as server, but as control point playing to a renderer and MMW was sending request(s) while the MMW close had been already initialized. That's fixed in 1860. BTW we already uses warning(s) when MMW is acting as control point (e.g. 'The %s player is turned off or inaccessible.'). |
|
|
Closing after revise Ludek is correct to not over complicate things and MWM gracefully closes as of 1860 |
