Hi Fred,
I just installed the 1.10. And with that one, I've an "unhandled exception" when I exit from BT (right click on the icon from the taskbar and clicked on the exit option)...
It's not a real problem as BT is working nice but... Never good anyway :-)
Also, I noticed you asked if we are using windows or wine under linux at the first start... Strange to ask that as wine should be "transparent" to the application...
There is not a way to simply avoid using certain function call if they don't exist or just write code in a different way who is natively compatible in both windows and wine ?
I read a topic about this quite interesting: http://forum.winehq.org/viewtopic.php?p=25906&sid=480c18ed9cad85e0f69bc386c736a2af
David.
Quote from: indians on June 30, 2011, 07:28:00 PM
There is not a way to simply avoid using certain function call if they don't exist or just write code in a different way who is natively compatible in both windows and wine ?
I did change the code in some places to work around Wine problems. In one instance Wine was Windows compatible, but Windows itself wasn't according to the doc.
The problem now lies in the Notices, the refresh isn't implemented or not working.
I tried several ways to work around this problem but couldn't find any. It's a wonder that it works at all, because it's active X that is only supported by IE.
When set to Linux it will still work on Windows, but you get a flicker at the notices refresh, as the whole page is destroyed and created again.
The crash at exit should be solved. It seems to be a sequencing problem, some parts close unpredictable. I now force my own sequence.
Installed 1.10 and it crashed about an hour later, at which point a Win7 (64) dialog popped up saying it was loading "compatibility settings" for BT. Haven't seen this one before.
Quote from: Beyond on July 01, 2011, 03:43:50 PM
Installed 1.10 and it crashed about an hour later, at which point a Win7 (64) dialog popped up saying it was loading "compatibility settings" for BT. Haven't seen this one before.
Can I get the crash report.
Quote from: fred on July 01, 2011, 03:47:31 PM
Quote from: Beyond on July 01, 2011, 03:43:50 PM
Installed 1.10 and it crashed about an hour later, at which point a Win7 (64) dialog popped up saying it was loading "compatibility settings" for BT. Haven't seen this one before.
Can I get the crash report.
Sorry, deleted. There haven't been any crashes since. If I get another one should I send it? Is there a smaller part of reports that could be sent? Slow DSL connection here :(
Quote from: Beyond on July 01, 2011, 05:04:11 PM
Sorry, deleted. There haven't been any crashes since. If I get another one should I send it? Is there a smaller part of reports that could be sent? Slow DSL connection here :(
No, the only one I can use is the one in the BoincTasks/crash folder. You should be able to zip them, they might get smaller. But maybe you don't see them anymore. ;D
I have bad test machines, haven't seen any crash in a long time.
Quote from: Beyond on July 01, 2011, 05:04:11 PM
Sorry, deleted.
There is no need to manually delete the crash files, as they are auto deleted after a period of time.
Quote from: fred on July 01, 2011, 07:10:02 AM
I did change the code in some places to work around Wine problems.
There is some ways to find if wine is used without asking the user... Some specific wine function calls can be found or simply by checking the environment variables for example...
Otherwise it could be a good challenge for you to write BT also for Linux... No wine problems anymore then ;-)
Quote from: fred on July 01, 2011, 07:10:02 AM
In one instance Wine was Windows compatible, but Windows itself wasn't according to the doc.
Thats why I don't like to write code under windows... It's always a pain to find reliable docs and even with them, windows itself don't follow them... what a mess :-) Linux world is a lot more "logic" and powerful in many ways and all documented. And in case of doubt, sources are easy to find :-) However, I would not recommend Linux for everyone... It stays a OS for advanced users anyway. Even if Ubuntu like Os becomes more attractive and easy to use.
Quote from: fred on July 01, 2011, 07:10:02 AM
The problem now lies in the Notices, the refresh isn't implemented or not working. I tried several ways to work around this problem but couldn't find any. It's a wonder that it works at all, because it's active X that is only supported by IE.
Wine implements also active X I think... They developed a clone of IE for that purpose I think...
Quote from: fred on July 01, 2011, 07:10:02 AM
The crash at exit should be solved. It seems to be a sequencing problem, some parts close unpredictable. I now force my own sequence.
If you want that I test it... No problem, just give me a link with your beta version fixed.
i also have a unhandled exception from right click, exit.
do you need it.
edit: noted
Quote from: dskrbt on July 05, 2011, 04:33:39 PM
i also have a unhandled exception from right click, exit.
do you need it.
I found a rather serious bug and one minor, that should cause crashes at exit. Tedious work for almost a whole day, finding the exact location. >:(
But 1.10 is more stable than I had expected, because of the thousands of code changes.
So better wait for 1.11.
Me too (a crash dump compressed to 38 MB is available if required):
QuoteBoincTasks
Sorry but BoincTasks has crashed.
Dump file created succesfully...
+
boinctasks64.exe - Fatal Application Exit
Unhandled Exception occured!
I'm not sure what exactly happened. I've resumed my computer from hibernation, unlocked my session. Win7 greeted me with crashed client and crashed BT. After confirming the dialogs, the Manager apparently started a new client (which successfully crunched a couple of hours till now), but never succeeded to connect it. The same with a newly started BT - it could no way connect to the client (6.12.33). The Manager's stdoutgui.txt is full of lines like
Quote[07/05/11 23:37:48] TRACE [11140]: init_asynch() connect: -1
[07/05/11 23:37:49] TRACE [11140]: init_asynch() boinc_socket: 56920
[07/05/11 23:37:49] TRACE [11140]: init_asynch() connect: -1
[07/05/11 23:37:49] TRACE [11140]: init_asynch() boinc_socket: 56924
[07/05/11 23:37:49] TRACE [11140]: init_asynch() connect: -1
[07/05/11 23:37:49] TRACE [11140]: init_asynch() boinc_socket: 56928
After exiting the Manager, both BT and a newly started Manager immediately connected the client.
Quote from: fred on July 05, 2011, 04:40:42 PM
Quote from: dskrbt on July 05, 2011, 04:33:39 PM
i also have a unhandled exception from right click, exit. do you need it.
I found a rather serious bug and one minor, that should cause crashes at exit. Tedious work for almost a whole day, finding the exact location. >:(
But 1.10 is more stable than I had expected, because of the thousands of code changes. So better wait for 1.11.
I have 3 but will wait until 1.11 and see how that goes.
im also getting an error when exiting on windows 7 64bit
Problem signature:
Problem Event Name: APPCRASH
Application Name: boinctasks64.exe
Application Version: 1.1.0.0
Application Timestamp: 4e0acfbe
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.17514
Fault Module Timestamp: 4ce7c78c
Exception Code: c000041d
Exception Offset: 000000000000a49d
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057
Additional Information 1: 9bbf
Additional Information 2: 9bbfcf63f2bc2266638c8cb88e254ddc
Additional Information 3: 5fe1
Additional Information 4: 5fe12703321fba2e2cfc153fa7220f27
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
Quote from: gabranth on July 06, 2011, 01:14:54 PM
im also getting an error when exiting on windows 7 64bit
V 1.11 will be out soon.
Don't you get a crash report? http://www.efmer.eu/forum_tt/index.php?topic=338.0 (http://www.efmer.eu/forum_tt/index.php?topic=338.0)