[Bug 51429] New: Sakura no Uta: spams RtlpWaitForCriticalSection
https://bugs.winehq.org/show_bug.cgi?id=51429 Bug ID: 51429 Summary: Sakura no Uta: spams RtlpWaitForCriticalSection Product: Wine Version: 6.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: pernegger(a)gmail.com Distribution: --- Created attachment 70281 --> https://bugs.winehq.org/attachment.cgi?id=70281 wine-6.12 terminal output Sakura on Uta will start spamming the terminal with ****:err:ntdll:RtlpWaitForCriticalSection section ******** "?" wait timed out in thread ****, blocked by 0024, retrying (60 sec) [* = hex digit.] right from the start. The attached log just runs from launching it to reaching the main menu seconds later. Unlike in #50577 there aren't any noticeable symptoms. Despite both games having "uta" in their name, this isn't a duplicate -- they use different engines. The upside is that Sakura no Uta has a free trial version that behaves exactly like the full version, so someone who knows what they're doing could have a closer look at this: https://www.makura-soft.com/sakuranouta/special/trial_download.html. The download links are labelled "ダウンロード", at the bottom of the page. Any one will do, assuming it works, they're just mirrors. It's likely you'll need to prefix the wine invocation with LANG=ja_JP.UTF-8 or so, at least if you want the text to show up properly. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51429 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID CC| |z.figura12(a)gmail.com --- Comment #1 from Zebediah Figura <z.figura12(a)gmail.com> --- FIXME or ERR messages in the terminal are not bugs. The relevant message often indicates a bug, but it may just as easily indicate a slow machine, or a poorly designed application. Please feel free to reopen if there is actual application misbehaviour. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51429 --- Comment #2 from pernegger(a)gmail.com --- Well, the log spam alone could be considered a bug. I highly doubt a 3900X with 32 GB RAM (not otherwise loaded) counts as slow in the context of running a visual novel. For reference, the listed minimum requirement is a Pentium 4 2 GHz, 1 GB RAM. It is of course very possible that the game is just buggy = behaves the same on Windows. At any rate my reasoning for reporting it was that this error seems to pop up in many games, whether they actually end up deadlocking or not, but it isn't a hundred percent reproducible in most cases, and the games costs money, so any debugging needs to go through the submitter. In other words, if there is an underlying problem in WINE, this might make for a nice test case. That said, I fully understand your side, too. I'll see if I can get it to manifest some actual symptoms on different hardware. Thanks for replying! :-) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51429 --- Comment #3 from Zebediah Figura <z.figura12(a)gmail.com> --- All that message means is that a thread has been blocked on a critical section for more than 5 seconds. A critical section is a sleeping mutex, but generally shouldn't be held for long periods of time, and if it does, it's probably application misbehaviour. But the "?" means that it's one the application created (not Wine), so whatever the application is doing to hold on to that CS is probably its own fault. Not certainly, but probably, and given there's nothing visibly wrong, it's not worth investigating. Most software in the Unix world is on a completely open-source stack, and is completely implemented at least according to its own specifications. As a result a log message either indicates a problem in the component itself, or in a higher or lower component, any of which deserve fixing. Wine is unique; we don't control the software that we run, and we can't fix its bugs. At the same time, large parts of Wine are simply not implemented, because no application has needed them yet. Hence it's very easy for applications to trigger ERR or FIXME messages meaning either that the application is doing something broken, or it's hitting a code path that isn't (fully) implemented in Wine. But often neither of these actually matter in practice. Hence we view log messages as a debugging aid—a FIXME *can* be harmless, or it can be the root cause of a failure—but not as a symptom of a bug in themselves (in most cases). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51429 André H. <nerv(a)dawncrow.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED CC| |nerv(a)dawncrow.de --- Comment #4 from André H. <nerv(a)dawncrow.de> --- closing invalid -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla