What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Entire DB Crash after second time press Trinity Config Button

righttang

New Member
Joined
Sep 9, 2012
Messages
78
Reaction score
3
This is a quite annoying issue and I did search the forum and it seems no one have that issue.
I have tried the clean install and tried different version of trinity, but it still get the same issue.

The issue I have is, I open the DB, input key, and enable the trinity plugin, click config.
Then I get the configuration window, I setup everything, and click Save settings, then start the bot. All good.

And I go back to Trinity config, the entire DB stop responding, it says: check for online solution or something.
The bot stopped and I have to close DB and logon to BuddyAuth to kill my session and and restart it.

That simply means, I get only one chance to configure Trinity everytime I start DB.

I tried following versions.
DB 349 + Trinity 1.8.17
DB 372 + Trinity 1.8.17
DB 372 + Trinity 1.8.13

All the same, and I attached DB log and Trinity Log
Code:
2014-04-08 09:43:23,719 [1] INFO  MainWindow (null) - DemonbuddyBETA v1.1.1760.372 started
2014-04-08 09:43:25,719 [7] INFO  MainWindow (null) - Logging in...
2014-04-08 09:43:26,969 [1] INFO  MainWindow (null) - Attached to Diablo III with pid: 4032
2014-04-08 09:43:26,983 [1] INFO  MainWindow (null) - Flashing window
2014-04-08 09:43:29,684 [1] DEBUG MainWindow (null) - Executable Path: C:\Users\TT\Desktop\DemonBuddy\Demonbuddy-371 - Trinity8.13\Demonbuddy.exe
2014-04-08 09:43:29,685 [1] DEBUG MainWindow (null) - OS Architecture: AMD64
2014-04-08 09:43:29,686 [1] DEBUG MainWindow (null) - OS: Windows 7 Service Pack 1 64-bit
2014-04-08 09:43:29,687 [1] DEBUG MainWindow (null) - OS Language: English (United States)
2014-04-08 09:43:29,728 [1] DEBUG AssemblyLoader`1 (null) - Reloading AssemblyLoader<Zeta.Common.Plugins.IPlugin> - Initializing plugins
2014-04-08 09:43:31,425 [1] INFO  Logger (null) - [Armory] v1.0.1 Initialized
2014-04-08 09:43:31,427 [1] INFO  Logger (null) - Setting up Trinity Logging
2014-04-08 09:43:31,478 [1] INFO  Logger (null) - [Trinity] Initialized v1.8.13
2014-04-08 09:43:31,813 [1] INFO  Logger (null) - [Armory] v1.0.1  Enabled
2014-04-08 09:43:31,821 [1] INFO  Logger (null) - [QuestTools] Plugin v1.5.0 Enabled
2014-04-08 09:43:31,827 [1] INFO  Logger (null) - [Trinity] OnEnable start
2014-04-08 09:43:31,835 [1] INFO  Logger (null) - [Trinity] Loading BattleTag Settings
2014-04-08 09:43:37,049 [1] INFO  Logger (null) - [Trinity] Configuration file loaded
2014-04-08 09:43:37,069 [1] DEBUG Logger (null) - [Trinity] Using Trinity Unstucker
2014-04-08 09:43:37,097 [1] INFO  Logger (null) - [Trinity] ENABLED: Trinity v1.8.13 now in action!
2014-04-08 09:43:37,098 [1] DEBUG MainWindow (null) - There are 3 plugins
2014-04-08 09:43:37,701 [1] DEBUG Logger (null) - [Trinity] Reset bot TPS to default
2014-04-08 09:43:38,293 [1] INFO  BotMain (null) - Current bot set to Order Bot
2014-04-08 09:43:38,294 [1] INFO  ProfileManager (null) - Loaded profile Act 2 by rrrix

Code:
19:43:31.455 DEBUG [Trinity] Initialized v1.8.13
19:43:31.827 DEBUG [Trinity] OnEnable start
19:43:31.833 DEBUG [Trinity] Plugin Check Watcher thread started
19:43:31.835 DEBUG [Trinity] Loading BattleTag Settings
19:43:37.049 DEBUG [Trinity] Configuration file loaded
19:43:37.069 DEBUG [Trinity] Using Trinity Unstucker
19:43:37.097 DEBUG [Trinity] ENABLED: Trinity v1.8.13 now in action!
19:43:37.098 DEBUG [Trinity] OnEnable took 5270.30126953125ms
19:43:37.701 DEBUG [Trinity] Reset bot TPS to default

Thanks in Advance
 
Confirmed!
You can only change setting once in Trinity. After you've saved them, if you want to open the config again, DB will crash.
 
.18 does the same, didnt test 17. .18 when you press stop, it goes in freeze mode, like you cant do anything or its invisible so i just end tasked it but .13 when you press stop, start works fine. But wasnt all trinity was you could change trinity settings only once? or was it different? i thought it was normal.
 
Confirmed
please solve it
don't ask just ask user to change a different vesion.
i tried all the versions.
 
It hasnt been this way in previous versions (long time ago), stopped gaming at that time. When I can back (around patch 2.0), DB had this issue. So somewhere along the line, this must have slipped in.
All versions since patch 2.0 seem to have this tho.
 
Same with trinity .20 (and previous versions) and latest DB beta.
 
What language, OS, OS Version, region?

Would anyone be interested in installing Visual Studio 2013 Express and trying to grab a stacktrace for me?
 
Using Windows 7 x64 English
Just let me know what you need me to do mate, and I'll be happy to help you get the info.
 
I just added a bunch of try/catch to all the UI related methods in Trinity 1.8.21 on SVN. If you're using that, let me know if it helps (and if it spits out any errors).
 
Glad someone posted about this. This has been happening to me as well in every version since I came back to Diablo with the 2.0.1 patch. Confirmed still happening with Trinity 1.8.21. Easily reproducible. What can I do to help debug it?

Using Windows 7 in a virtual machine on an almost brand new MBP.
 
Nightmare, can you post a log using 1.8.21?
 
Nightmare, can you post a log using 1.8.21?

Happy to help with whatever I can, though I'm not sure what files you need. Just PM me and tell me what files you're looking for and I'll send them over.
 
Still getting this on 1.8.21 also. It's whenever you go to Plugins, then click on Trinity, then on another plugin, then back on Trinity, as well as when you open Trinity's configuration, close it, and then open it again. I have no idea what the problem could be. It's been an issue since at least 1.8.18, possibly earlier.

Here's the log file, which didn't seem to be useful, but it's there as SOP.

View attachment 3972 2014-04-16 18.41.txt

Also, here's the error Windows gave (System.InvalidOperationException). Maybe it's a Demonbuddy issue?
Code:
Problem signature:
  Problem Event Name: CLR20r3
  Problem Signature 01: demonbuddy.exe
  Problem Signature 02: 1.1.1788.355
  Problem Signature 03: 53471352
  Problem Signature 04: PresentationFramework
  Problem Signature 05: 4.0.0.0
  Problem Signature 06: 51eea94f
  Problem Signature 07: 369
  Problem Signature 08: 32
  Problem Signature 09: System.InvalidOperationException
  OS Version: 6.1.7601.2.1.0.256.1
  Locale ID: 1033
  Additional Information 1: 0a9e
  Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
  Additional Information 3: 0a9e
  Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

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

Side note: It may only be crashing on users using a VM. I'm using it on both a VM and the host, and the DemonBuddy on the host doesn't crash.
 
Last edited:
All mine have been crashing since RoS. You can go into trinity once, after that just clicking the "trinity" under plugins will typically crash db. If not hitting config will crash it 100%.
 
mine two similar PC (win7pro x64) behave different - one have problem & another have not. I tried many different sequences of actions - no luck
reinstall components or DB dont fix
db logs not contain any helpful info
 
is there anything i can do to help you fix this problem?

vista 64
 
Back
Top