Author Topic: Tox protocol  (Read 81461 times)

0 Members and 2 Guests are viewing this topic.

Offline unsane

  • Developer
  • *****
  • Posts: 155
  • Country: ru
  • Karma: 10
Re: Tox protocol
« Reply #240 on: 12 08 2015, 18:57:22 »
Vulpix, try r14926
Si no estas con nosotros, estas contra nosotros.
 

Offline Vulpix

  • Beta Tester
  • *****
  • Posts: 620
  • Country: 00
  • Karma: 15
Re: Tox protocol
« Reply #241 on: 13 08 2015, 07:14:22 »
@unsane, thanks! That worked. I also see you put in a new toxcore and changed some stuff regarding transfers. I was having some transfer issues before where a transfer would just never start properly, so hopefully this helps! I'll let you know if I run into any problems again.

Thanks!
 

Offline Wishmaster

  • Developer
  • Global Moderator
  • *****
  • Posts: 650
  • Country: de
  • Karma: 31
  • Anti-Hero
  • Version Info
Re: Tox protocol
« Reply #242 on: 14 08 2015, 16:14:08 »
Be careful! tox.im, toxme.se and libtoxcore.so are under control of an attacker. Do not use them. New project website is https://tox.chat
 

Offline Vulpix

  • Beta Tester
  • *****
  • Posts: 620
  • Country: 00
  • Karma: 15
Re: Tox protocol
« Reply #243 on: 14 08 2015, 19:21:01 »
Well, it's not really an attacker. It's a drama that popped up a while back, involving a person called Sean Qureshi (aka Stqism, aka AlexStraunoff, aka NikolaiToryzin) who proved to be unreliable and stole some (I think something around $3k or $1.5k not sure anymore) of the funds raised for the tox project. He owns / runs those sites and effectively holds them hostage, refusing anyone else to control them. This is why the tox project decided to detach themselves from this person and they made the new site.

More info here:
https://blog.tox.chat/2015/07/current-situation-3/

New website is indeed https://tox.chat/ , same with the new toxme service which is now https://toxme.io/ ; it works just the same though.

@unsane - could you please integrate toxme.io for the user search ? Thanks!
 

Offline unsane

  • Developer
  • *****
  • Posts: 155
  • Country: ru
  • Karma: 10
Re: Tox protocol
« Reply #244 on: 15 08 2015, 10:14:45 »
@unsane - could you please integrate toxme.io for the user search ?
r14957.
Si no estas con nosotros, estas contra nosotros.
 

Offline Vulpix

  • Beta Tester
  • *****
  • Posts: 620
  • Country: 00
  • Karma: 15
Re: Tox protocol
« Reply #245 on: 15 08 2015, 12:39:27 »
Wow you're quick! I'll check it out tomorrow when the binary is up in the repo. Thanks!
 

Offline Corak

  • Jr. Member
  • **
  • Posts: 93
  • Country: ru
  • Karma: 8
  • IDDQD
    • Corak's Software Incorporated
  • Jabber ID
  • Version Info
Re: Tox protocol
« Reply #246 on: 26 08 2015, 06:27:12 »
Пак свежих крашей по Tox:

Code: [Select]
Exception: Access Violation at address 13DB2C12. Reading from address 06C038CC.

Stack Trace:
---------------------------------------------------------------
13DB2C12 (libtox 13DA0000): ..\toxcore\TCP_client.c (951): do_TCP_connection
13DB47EB (libtox 13DA0000): ..\toxcore\TCP_connection.c (64): do_tcp_connections
13DC2B08 (libtox 13DA0000): ..\toxcore\net_crypto.c (1855): do_net_crypto
1224C4D1 (mir_core 12240000): e:\sources\miranda_ng_compilation\src\mir_core\src\threads.cpp (154): forkthreadex_r
78AFC556 (MSVCR100 78AA0000): (filename not available) (0): endthreadex
78AFC600 (MSVCR100 78AA0000): (filename not available) (0): endthreadex
7C80B729 (kernel32 7C800000): (filename not available) (0): GetModuleFileNameA

+ http://trac.miranda-ng.org/ticket/1001

Code: [Select]
Exception: Access Violation at address 13DB0F3A. Reading from address 000008C0.

Stack Trace:
---------------------------------------------------------------
13DB0F3A (libtox 13DA0000): ..\toxcore\Messenger.c (2282): do_messenger
1224C4D1 (mir_core 12240000): e:\sources\miranda_ng_compilation\src\mir_core\src\threads.cpp (154): forkthreadex_r
78AFC556 (MSVCR100 78AA0000): (filename not available) (0): endthreadex
78AFC600 (MSVCR100 78AA0000): (filename not available) (0): endthreadex
7C80B729 (kernel32 7C800000): (filename not available) (0): GetModuleFileNameA


Code: [Select]
Likely cause of the crash plugin: Tox protocol
Exception: Access Violation at address 17181083. Reading from address 012BA000.
Stack Trace:
---------------------------------------------------------------
17181083 (Tox 17180000): e:\sources\miranda_ng_compilation\protocols\tox\src\tox_address.h (88): ToxBinAddress::ToxBinAddress
1718BDC7 (Tox 17180000): e:\sources\miranda_ng_compilation\protocols\tox\src\tox_network.cpp (12): CToxProto::BootstrapNode
1718C1C3 (Tox 17180000): e:\sources\miranda_ng_compilation\protocols\tox\src\tox_network.cpp (67): CToxProto::BootstrapNodesFromIni
1718C2BE (Tox 17180000): e:\sources\miranda_ng_compilation\protocols\tox\src\tox_network.cpp (85): CToxProto::BootstrapNodes
1718C3E1 (Tox 17180000): e:\sources\miranda_ng_compilation\protocols\tox\src\tox_network.cpp (133): CToxProto::CheckConnection
1718C46E (Tox 17180000): e:\sources\miranda_ng_compilation\protocols\tox\src\tox_network.cpp (175): CToxProto::PollingThread
1224C4D1 (mir_core 12240000): e:\sources\miranda_ng_compilation\src\mir_core\src\threads.cpp (154): forkthreadex_r
78AFC556 (MSVCR100 78AA0000): (filename not available) (0): endthreadex
78AFC600 (MSVCR100 78AA0000): (filename not available) (0): endthreadex
7C80B729 (kernel32 7C800000): (filename not available) (0): GetModuleFileNameA

+ http://trac.miranda-ng.org/ticket/1002

Code: [Select]
Exception: Access Violation at address 13DBE63B. Reading from address 0000000C.

Stack Trace:
---------------------------------------------------------------
13DBE63B (libtox 13DA0000): ..\toxcore\group.c (2266): kill_groupchats
1224C4D1 (mir_core 12240000): e:\sources\miranda_ng_compilation\src\mir_core\src\threads.cpp (154): forkthreadex_r
78AFC556 (MSVCR100 78AA0000): (filename not available) (0): endthreadex
78AFC600 (MSVCR100 78AA0000): (filename not available) (0): endthreadex
7C80B729 (kernel32 7C800000): (filename not available) (0): GetModuleFileNameA


Code: [Select]
Exception: Access Violation at address 13DCAD91. Reading from address 08199C18.

Stack Trace:
---------------------------------------------------------------
13DCAD91 (libtox 13DA0000): ..\toxcore\onion_client.c (1435): do_onion_client
1224C554 (mir_core 12240000): e:\sources\miranda_ng_compilation\src\mir_core\src\threads.cpp (154): forkthreadex_r
78AFC556 (MSVCR100 78AA0000): (filename not available) (0): endthreadex
78AFC600 (MSVCR100 78AA0000): (filename not available) (0): endthreadex
7C80B729 (kernel32 7C800000): (filename not available) (0): GetModuleFileNameA
« Last Edit: 05 09 2015, 10:39:32 by Corak »
 

Offline Vulpix

  • Beta Tester
  • *****
  • Posts: 620
  • Country: 00
  • Karma: 15
Re: Tox protocol
« Reply #247 on: 03 09 2015, 11:45:34 »
This is very strange Corak.

What's your OS?

Can you post a complete version info of your miranda?

Thanks
 

Offline Corak

  • Jr. Member
  • **
  • Posts: 93
  • Country: ru
  • Karma: 8
  • IDDQD
    • Corak's Software Incorporated
  • Jabber ID
  • Version Info
Re: Tox protocol
« Reply #248 on: 03 09 2015, 16:10:00 »
Windows XP SP3 32bit.
Easly: http://vi.miranda-ng.org/ru/detail/Corak
 

Offline Vulpix

  • Beta Tester
  • *****
  • Posts: 620
  • Country: 00
  • Karma: 15
Re: Tox protocol
« Reply #249 on: 03 09 2015, 16:38:42 »
I'll test it in my winxp home sp3 virtual machine.

It just randomly crashes after some time, right?
 

Offline Corak

  • Jr. Member
  • **
  • Posts: 93
  • Country: ru
  • Karma: 8
  • IDDQD
    • Corak's Software Incorporated
  • Jabber ID
  • Version Info
Re: Tox protocol
« Reply #250 on: 03 09 2015, 20:36:23 »
It WAS crashing after reconnection (click "Fix" on your active network connection, it will offline, then online). But now it seems not nessary - I tested latest alpha build and Unsane (developer) seems fixed all those crashes - no problems now.
 

Offline Corak

  • Jr. Member
  • **
  • Posts: 93
  • Country: ru
  • Karma: 8
  • IDDQD
    • Corak's Software Incorporated
  • Jabber ID
  • Version Info
Re: Tox protocol
« Reply #251 on: 04 09 2015, 17:30:25 »
I been wrong - still not fixed. When I tried to reconnect (rebooted wifi my router):

Crashlog 1
Code: [Select]
"Exception: Access Violation at address 13DBE63B. Reading from address 0000000C.

Stack Trace:
---------------------------------------------------------------
13DBE63B (libtox 13DA0000): ..\toxcore\group.c (2266): kill_groupchats
1224C554 (mir_core 12240000): e:\sources\miranda_ng_compilation\src\mir_core\src\threads.cpp (154): forkthreadex_r
78AFC556 (MSVCR100 78AA0000): (filename not available) (0): endthreadex
78AFC600 (MSVCR100 78AA0000): (filename not available) (0): endthreadex
7C80B729 (kernel32 7C800000): (filename not available) (0): GetModuleFileNameA"


+ New crash, in attach:
Crashlog 2
Code: [Select]
Exception: Access Violation at address 13DB10DB. Reading from address 00000008.
Stack Trace:
---------------------------------------------------------------
13DB10DB (libtox 13DA0000): ..\toxcore\Messenger.c (2544): messenger_size
171EFF0D (Tox 171E0000): e:\sources\miranda_ng_compilation\protocols\tox\src\tox_core.cpp (118): CToxProto::UninitToxCore
171EC603 (Tox 171E0000): e:\sources\miranda_ng_compilation\protocols\tox\src\tox_network.cpp (179): CToxProto::PollingThread
1224C554 (mir_core 12240000): e:\sources\miranda_ng_compilation\src\mir_core\src\threads.cpp (154): forkthreadex_r
78AFC556 (MSVCR100 78AA0000): (filename not available) (0): endthreadex
78AFC600 (MSVCR100 78AA0000): (filename not available) (0): endthreadex
7C80B729 (kernel32 7C800000): (filename not available) (0): GetModuleFileNameA
« Last Edit: 05 09 2015, 14:59:26 by Corak »
 

Offline Vulpix

  • Beta Tester
  • *****
  • Posts: 620
  • Country: 00
  • Karma: 15
Re: Tox protocol
« Reply #252 on: 05 09 2015, 09:32:11 »
Corak, I suspect that it's because of KeepStatus, or KeepStatus helps reproduce it when it tries to reconnect multiple times after a loss of internet connection - it doesn't give tox enough time to bootstrap.

Can you please disable KeepStatus for tox (or disable it completely) and only handle reconnections manually, see if it still occurs?
 

Offline Corak

  • Jr. Member
  • **
  • Posts: 93
  • Country: ru
  • Karma: 8
  • IDDQD
    • Corak's Software Incorporated
  • Jabber ID
  • Version Info
Re: Tox protocol
« Reply #253 on: 05 09 2015, 10:49:49 »
Yes, you are right - keepstatus helps to repeat this crash easly - or just fast enough user reaction to switch online/offline status. Disable it, and it's hard now to repeat this crash if it changed manually after some timeouts.. But anyway I sure this crashes must be fixed - keepstatus are really nessary plugin, because protocols and their connections are still very UnStable, so every of them can go offline every minute and never return back automatically, so you will have a bad time swiching it back manually.
« Last Edit: 05 09 2015, 10:51:33 by Corak »
 

Offline Vulpix

  • Beta Tester
  • *****
  • Posts: 620
  • Country: 00
  • Karma: 15
Re: Tox protocol
« Reply #254 on: 05 09 2015, 12:00:51 »
I agree, but I noticed some crashes before with steam when I had KeepStatus set too aggressively.

@unsane - one more thing. The recent notification "unable to load tox profile" shows up if you enable ipv6 on windowsXP without a working teredo stack - it's a bit confusing since it says unable to load profile, but it should say unable to connect via ipv6 or something similar. Can you please also look at that in addition to those errors from Corak?

Thanks!