win: currency symbol detection fail leads to crash

Bug #1862540 reported by Ivan Kouvykov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
HomeBank
Fix Released
Medium
Maxime DOYEN

Bug Description

OS: Microsoft Windows 10 Enterprise 10.0.18363 Build 18363 (x64-based PC)

I've just installed HomeBank for the fist time on my system. When I try to start the application, I see the splash screen, outline of the main window, then both disappear (the application crashes).

Tried both the previous (5.2.8) and the current (5.3.1) versions of HomeBank - behaviour is the same.

"gtk3-widget-factory.exe" start and runs successfully.

Revision history for this message
Ivan Kouvykov (ayevee) wrote :

Upgraded HomeBank to 5.3.2 - still have this issue.

Revision history for this message
Maxime DOYEN (mdoyen) wrote :

Not reproducible so far, so it might be related to your PC or something installed/running on your PC.

Are you able to test the same installer on another Windows computer ?

Changed in homebank:
status: New → Incomplete
Revision history for this message
Ivan Kouvykov (ayevee) wrote :

Yes, but not immediately. Will do in a couple of days.

Meanwhile - if it's something specific to my PC - any ideas where to start troubleshooting?

Revision history for this message
Ivan Kouvykov (ayevee) wrote :

Upd. I have two messages in Windows Event Log (one Error and one Information) + a link to report file. Attached all.

Revision history for this message
Ivan Kouvykov (ayevee) wrote :
Revision history for this message
Ivan Kouvykov (ayevee) wrote :
Revision history for this message
Ivan Kouvykov (ayevee) wrote :
Revision history for this message
Maxime DOYEN (mdoyen) wrote :

OK let go for a debug session:

please download gdb here:
- http://homebank.free.fr/public/hb_gdb.zip
- http://homebank.free.fr/public/HomeBank_debug.zip
- unzip to C:\Program Files (x86)\HomeBank

- on the folder location, replace C:\Program Files (x86)\HomeBank by cmd + press enter (or open a cmd.exe to that location

launch the debug session with: gdb.exe HomeBank_debug.exe
- type: run + enter (this will launch Homebank)
- go to the step into HomeBank until crash
- HomeBank will freeze, don't close it
- go back to the cmd console, you should have focus
- type 'bt' + enter
- this will log the debug log and hopefully the crash location/dll area
- post that report as an attached file here

Revision history for this message
Ivan Kouvykov (ayevee) wrote :

Maxime,

> Are you able to test the same installer on another Windows computer ?
Tried installing version 5.3.2 on another Windows computer - HomeBank runs successfully. So I guess you are right the problem is specific to my PC indeed.

> OK let go for a debug session
Done, dbg output attached.

Revision history for this message
Maxime DOYEN (mdoyen) wrote :

Hello Ivan,

Thanks for those first sets of info, we are on the track.
Can you run this debug one that will display some more info and hoppefully not crash, en add the txt output here ?

the bug is that the symbol currency extracted from your windows fails, and leave inconsistent data into the default curency, and so there is something I need to fix here, with addisiotnnal controls, but I need to understand this case first with the next info you will provide, the print should display what your system provide.

Thanks
Max.

Maxime DOYEN (mdoyen)
Changed in homebank:
importance: Undecided → Medium
assignee: nobody → Maxime DOYEN (mdoyen)
Revision history for this message
Ivan Kouvykov (ayevee) wrote :

Maxime,

With new debug version HomeBank starts successfully. GDB output attached.

Maxime DOYEN (mdoyen)
Changed in homebank:
status: Incomplete → Confirmed
milestone: none → 5.3.3
Maxime DOYEN (mdoyen)
summary: - Fresh installation crashes on startup
+ win: currency symbol detection fail leads to crash
Maxime DOYEN (mdoyen)
Changed in homebank:
milestone: 5.3.3 → 5.4
Maxime DOYEN (mdoyen)
Changed in homebank:
status: Confirmed → Fix Committed
Maxime DOYEN (mdoyen)
Changed in homebank:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.