[Bug 40156] New: AutoWikiBrowser database scanner fails with "no access to memory location"
https://bugs.winehq.org/show_bug.cgi?id=40156 Bug ID: 40156 Summary: AutoWikiBrowser database scanner fails with "no access to memory location" Product: Wine Version: 1.8 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rjwilmsi(a)gmail.com Distribution: --- Created attachment 53658 --> https://bugs.winehq.org/attachment.cgi?id=53658 System.IO.__Error.WinIOError at System.Xml.XmlReader.ReadToFollowing Running the AutoWikiBrowser database scanner fails with "no access to memory location" normally within seconds of scan starting. Occurs on wine wine-1.8.1 and wine-1.7.39 To reproduce: export WINEARCH=win32 winetricks -q msxml3 dotnet35 corefonts gdiplus riched20 ie6 [Probably only dotnet35 is required for this testing] download AutoWikiBrowser from http://sourceforge.net/projects/autowikibrowser/ choose latest version (5.8.5.1 at time of writing). unzip AutoWikiBrowser and run wine AutoWikiBrowser.exe choose Tools -> Database scanner download a wikipedia database dump file from https://dumps.wikimedia.org/ browse to the database XML file search based on title contains 'foo' or other option. Press Start. Wait for scan to progress. Scan normally fails within seconds with "no access to memory location" error (stack trace relating to C# XML reader attached). The problem only intermittently occurs on smaller XML dump files (e.g. < 100 MB uncompressed) but always occurs on large XML files. Above process works without error under Mono version 4 on same machine (using 50 GB English wikipedia XML dump file) and of course on native Windows. Possible further information/speculation: I have written a simple single threaded console only .NET 2 exe that works under same wine setup without this error on same machine. So I suspect that the issue may be to do with multithreading: the AutoWikiBrowser scanner is multithreaded, versions of the test console exe I wrote failed with same error if I added multithreading. -- 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=40156 Sebastian Lackner <sebastian(a)fds-team.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian(a)fds-team.de --- Comment #1 from Sebastian Lackner <sebastian(a)fds-team.de> --- Could you please check if this issue already occurs with Staging versions? This sounds a bit like an issue with write watches, which means it would be a duplicate of an other bug. -- 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=40156 --- Comment #2 from rjwilmsi(a)gmail.com --- I'm not 100% sure about wine staging as I've not used it before. What I did (as using opensuse leap) is download wine 1.9.3 from http://download.opensuse.org/repositories/Education/openSUSE_Leap_42.1/ which at the time of writing is the latest version available. I then removed .wine/, re-did winetricks, ran wineboot and then retested: no difference, still get same "no access to memory location" error. -- 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=40156 --- Comment #3 from rjwilmsi(a)gmail.com --- Retesting as after a couple of years there are newer wine versions: wine 2.0.1 with winetricks dotnet20 => fail, same error as before wine 2.0.1 with winetricks dotnet40 => fail, same error as before wine 3.5 with winetricks dotnet40 => success, database scan completes without error (Jan 2018 enwiki, ~60 GB XML). So from my testing issue has been resolved at some point between wine 2.0.1 and 3.5, so thanks to wine team. -- 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=40156 rjwilmsi(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #4 from rjwilmsi(a)gmail.com --- As above -- 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=40156 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #5 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 3.6. -- 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)
-
wine-bugs＠winehq.org