MCV-Software / TWBlue

TWBlue, an accessible, open source and multiplatform twitter application.
GNU General Public License v2.0
59 stars 36 forks source link

Unable to use latest 64 bit portable version #514

Open CoBC opened 1 year ago

CoBC commented 1 year ago

Hi, when I try to use the latest TWBlue 64 bit portable version on Windows 11, its result with a strange behavior, the GUI doesn't work, process appears in task manager, I have no error on error.log, and the last line in debug.log is "initializing output subsystem". No problem with 32 bit portable. Thanks.

mhussaincov93 commented 1 year ago

hi, I would like to chip in on this with the same issue. well it's slightly different, my version is installed. some statts. mem usage for the stawled twblue process is 67288k this is the same mem usage weather it's left running for along time or not. if the other commentore could do us a faver, please tell us the exact mem usage of the problematic twblue process after lieveing it for 4 minutes? is it the same? i'm running on windows server 2022, that should not really matter in this case. i'm running the very latest 64 bit version of twblue from the site. my debug log below. nuthing is in the error log.

i'll add more after i've tryed a few things out. 05/04/2023 04:41:39 main DEBUG: Starting TWBlue 2023.02.08 05/04/2023 04:41:39 config DEBUG: Loading global app settings... 05/04/2023 04:41:39 config DEBUG: Loading keymap... 05/04/2023 04:41:39 main DEBUG: Using Windows 64bit 05/04/2023 04:41:39 main DEBUG: Application path is C:\Program Files\twblue 05/04/2023 04:41:39 main DEBUG: config path is C:\Users\Administrator\AppData\Roaming\TW Blue\config 05/04/2023 04:41:39 sound DEBUG: creating stream URL player... 05/04/2023 04:41:39 sound DEBUG: URL Player initialized 05/04/2023 04:41:39 core.output DEBUG: Initializing output subsystem.

after that last message, complete freeze, no window is displayed, just what seembs to be a zombie twblue process which states running. so I can assume, that something's stalled in execution process? I hope this helps in debugging this. the only way i've found of temproarlly fixing this was to install the same twblue version over the non functional version. here's my twblue.conf pasted below incase this helps.

[sessions] current_session = 241832 sessions = , ignored_sessions = ,

[app-settings] language = system update_period = 1 hide_gui = False voice_enabled = False ask_at_exit = True autostart = False handle_longtweets = False use_invisible_keyboard_shorcuts = True play_ready_sound = True speak_ready_msg = True log_level = error load_keymap = Windows 10.keymap donation_dialog_displayed = True check_for_updates = True remember_mention_and_longtweet = False longtweet = False mention_all = False no_streaming = True

[proxy] type = 0 server = "" port = 8080 user = "" password = ""

and my session.conf excludeing my access tocun/key what ever it's colled.

instance = https://mastodon.social user_name = mhussaincov93 ignored_clients = ,

[general] relative_times = True read_preferences_from_instance = True max_posts_per_call = 40 reverse_timelines = False persist_size = -1 load_cache_in_memory = True show_screen_names = False hide_emojis = False buffer_order = home, local, mentions, direct_messages, sent, favorites, bookmarks, followers, following, blocked, muted, notifications boost_mode = ask disable_streaming = False

[sound] volume = 1.0 input_device = Default output_device = Default session_mute = False current_soundpack = FreakyBlue indicate_audio = True indicate_img = True

[other_buffers] timelines = 109383126830037443, 109409808340146175, 109362027432997159, 109288028220200633, 109365957647672639, 109830528517806034, 109380704943607791, 109332819722078014, 109365930748981877, 109294074283199367, 110113824909387467, 109845439670034767, 109825687111053895, 109514448274842672, 109288075101170190, 109362013227296831, 882021, 109362134559903607, 31166, 109430104878839192, 109385135064422968, 108199416260370505, 109362662223616118, 29822, 109359994198154877, 109323571151998278, 267694 searches = , lists = , followers_timelines = , following_timelines = 109362013227296831, 109430104878839192 trending_topic_buffers = , muted_buffers = , autoread_buffers = mentions, direct_messages, events

[mysc] spelling_language = "" save_followers_in_autocompletion_db = False save_friends_in_autocompletion_db = False ocr_language = ""

[reporting] braille_reporting = True speech_reporting = True

[templates] post = "$display_name, $safe_text $image_descriptions $date. $visibility. $source" person = "$display_name (@$screen_name). $followers followers, $following following, $posts posts. Joined $created_at." conversation = Conversation with $users. Last message: $last_post notification = "$display_name $text, $date"

[filters]

[user-aliases]

Majid

mhussaincov93 commented 1 year ago

hi, an update. not sure if this matters. made an archive of my config. deleted the twblue folder in %appdata% relaunched the twblue. memory usage is now 67360k and is fluctuateing. no window is being displayed. like last time. the log displayes the same process till it halts. just a stab in the dark, could this be something to do with the output subsystem? Majid

mhussaincov93 commented 1 year ago

32 bit version of twblue works indeed, with my old config. I would be greatful if this could be looked in to. Majid

manuelcortez commented 1 year ago

I'm unable to reproduce. It seems issue comes from AO2. But not sure why it happens only in certain devices.

mhussaincov93 commented 1 year ago

what is AO2?

mhussaincov93 commented 1 year ago

and is there anything I could do at my end to use the 64 bit builds again? windows version?