http://bugs.winehq.org/show_bug.cgi?id=18569
Summary: TeamViewer: App doesn't start, probably heap corruption Product: Wine Version: 1.1.21 Platform: PC URL: http://www.teamviewer.com/download/TeamViewer_Setup.ex e OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: scpan@live.fr
Created an attachment (id=21230) --> (http://bugs.winehq.org/attachment.cgi?id=21230) Result of WINEDEBUG=+relay,+seh,+tid wine TeamViewer.exe &>/tmp/relay.txt
I installed TeamViewer with the default options. At the end the cursor blinks forever so I ctrl-c it.
I moved to the working directory and tried to launch TeamViewer with: wine TeamViewer.exe The app doesn't start and I get an error in terminal (check attach)
I went to #winehq irc to find help, I did steps below :
I removed my .wine directory and re-installed TeamViewer: same error I did a trace log with WINEDEBUG=+relay,+seh,+tid wine TeamViewer.exe &>/tmp/relay.txt and lzma -9 /tmp/relay.txt You can find the trace log in attachment Focht thinks it's because of a heap corruption, I did WINEDEBUG=+relay,+seh,+tid,+heap wine TeamViewer.exe &>/tmp/relay.txt and TeamViewer launches succesfully but it doesn't lauch with WINEDEBUG=warn+heap wine ./TeamViewer.exe
So I now use WINEDEBUG=+seh,+tid,+heap wine TeamViewer.exe &>/tmp/relay.txt for a workaround but still looking for a fix.
http://bugs.winehq.org/show_bug.cgi?id=18569
--- Comment #1 from Sicheng PAN scpan@live.fr 2009-05-22 08:49:25 --- Created an attachment (id=21231) --> (http://bugs.winehq.org/attachment.cgi?id=21231) Output of "wine TeamViewer.exe"
http://bugs.winehq.org/show_bug.cgi?id=18569
Sicheng PAN scpan@live.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #21231|application/octet-stream |application/txt mime type| | Attachment #21231|ircbug |tmoutput.txt filename| |
http://bugs.winehq.org/show_bug.cgi?id=18569
--- Comment #2 from Sicheng PAN scpan@live.fr 2009-05-22 08:59:19 --- Btw my distro is Archlinux 32bits, wine package is from its repository.
http://bugs.winehq.org/show_bug.cgi?id=18569
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download
http://bugs.winehq.org/show_bug.cgi?id=18569
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net
--- Comment #3 from Anastasius Focht focht@gmx.net 2009-05-30 15:54:08 --- Hello,
as I've already said in #winehq - such bugs are very difficult to diagnose due their nature.
I looked again at this thing and it most likely seems to be an application bug which Wine unearths due to different heap management/locking strategy in combination with different multithreading profile (thread timing).
There are C++ class members which get concurrently accessed/modified from different threads. Although the app implements locking by using critical sections there are very small time frames (code sections) where the locking strategy is uneffective due to thread timing. It really matters when threads really begin to execute their worker function and how long they take.
This has direct consequence on the app's heap management. Because a shared heap is used for all threads by default (msvc), failure to properly guard allocations/deallocations will introduce heap corruption.
The reason why +heap or +relay works here is that it modifies thread timing in a subtile way (when workers start and end), preventing heap management races.
--- Can you try the following: use 'winecfg', set version to "Windows NT4" and check if it improves the situation for you...
Background: OS < Win2K forces the msvc heap allocator the app is linked with to a more conservative strategy which involves more locking. The might prevent heap corruption resulting from multithreaded heap allocation races in certain situations.
Regards
http://bugs.winehq.org/show_bug.cgi?id=18569
--- Comment #4 from Sicheng PAN scpan@live.fr 2009-05-30 16:10:36 --- Created an attachment (id=21423) --> (http://bugs.winehq.org/attachment.cgi?id=21423) Terminal output after successfully launch of TeamViewer with Win NT4.0
TeamViewer launches successfully with setting Windows NT4.0 in winecfg, it seems to work fine. You can find the new terminal output in attachments. I didn't understood every thing Focht said but I really thanks him for the help he provided me.
http://bugs.winehq.org/show_bug.cgi?id=18569
Nils Andresen andresen.nils@googlemail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |andresen.nils@googlemail.co | |m
--- Comment #5 from Nils Andresen andresen.nils@googlemail.com 2009-07-19 14:16:56 --- I can confirm this issue - including that it can be resolved by setting Version to WinNT40.
http://bugs.winehq.org/show_bug.cgi?id=18569
mst@collogia.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mst@collogia.de
--- Comment #6 from mst@collogia.de 2009-09-06 14:22:11 --- Hi,
just tested Teamviewer 4.1.6597 with Wine 1.1.29. I can confirm that setting operating system to Windows NT will launch the application without any issues. Contrary to the posts before I have successfully launched Teamviewer in Windows XP mode. Sadly this only works every second try. About half of my teamviewer starts end with the above mentioned error.
Best regards
http://bugs.winehq.org/show_bug.cgi?id=18569
Janusz sunmake@wp.pl changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sunmake@wp.pl
--- Comment #7 from Janusz sunmake@wp.pl 2009-10-15 18:07:41 --- just tested Teamviewer 4.1.6597 with Wine 1.1.31 To launch in Windows XP mode,after the first use app I've done: /home/name/.wine/dosdevices/c:/users/name/temp/TeamViewer/Version4 run TeamViewer_.exe.That launch Setup-choice Run than accept Licence Agreement-done!Working.
http://bugs.winehq.org/show_bug.cgi?id=18569
--- Comment #8 from Janusz sunmake@wp.pl 2009-10-17 15:36:06 --- just tested Teamviewer 4.1.6597 with Wine 1.1.31 under Wine windows 4.NT & Windows 2003 install/unistall and works.
http://bugs.winehq.org/show_bug.cgi?id=18569
Benjamin Debski benjamin.debski@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |benjamin.debski@gmail.com
--- Comment #9 from Benjamin Debski benjamin.debski@gmail.com 2011-10-08 21:09:46 CDT --- Starts fine in Wine 1.3.29 I was able to connect to their test machine no problem, no special wine options needed.
http://bugs.winehq.org/show_bug.cgi?id=18569
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |00cpxxx@gmail.com
--- Comment #10 from Bruno Jesus 00cpxxx@gmail.com 2011-10-09 07:04:33 CDT --- Confirming fixed too. Tested using a clean prefix and team viewer versions 4 and 6 using winecfg win nt4, xp and win7.
http://bugs.winehq.org/show_bug.cgi?id=18569
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |adys.wh@gmail.com Resolution| |FIXED
--- Comment #11 from Jerome Leclanche adys.wh@gmail.com 2012-02-26 13:15:58 CST --- Reported fixed.
http://bugs.winehq.org/show_bug.cgi?id=18569
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #12 from Alexandre Julliard julliard@winehq.org 2012-03-02 13:01:49 CST --- Closing bugs fixed in 1.4-rc6.
-
wine-bugs＠winehq.org