http://bugs.winehq.org/show_bug.cgi?id=30873
Bug #: 30873 Summary: BMFont crashes on visualise option or save bitmap font as Product: Wine Version: 1.5.6 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: usp10 AssignedTo: wine-bugs@winehq.org ReportedBy: dav75uk@yahoo.co.uk Classification: Unclassified
Created attachment 40456 --> http://bugs.winehq.org/attachment.cgi?id=40456 Crash log
Run BMFont on a 64 bit system (http://www.angelcode.com/products/bmfont/) and select 000000 Latin + Latin Supplement. Click visualise or try to 'save bitmap font as' and a dialog indicate a crash opens.
This was seen with winetricks usp10 and after an update to 1.5.6 (which I assume overwrites winetricks' effect).
Log attached.
http://bugs.winehq.org/show_bug.cgi?id=30873
David dav75uk@yahoo.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Platform|x86 |x86-64
http://bugs.winehq.org/show_bug.cgi?id=30873
GyB gyebro69@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download Status|UNCONFIRMED |NEW URL| |http://www.angelcode.com/pr | |oducts/bmfont/install_bmfon | |t_1.12.exe CC| |gyebro69@gmail.com Component|usp10 |-unknown Ever Confirmed|0 |1
--- Comment #1 from GyB gyebro69@gmail.com 2012-06-09 23:56:15 CDT --- There is no proof yet that it is a problem with usp10 (changing component back to unknown). I can reproduce the crash on my system (Fedora 17 32 bit) and with a clean wineprefix. When you select Latin + Latin Supplement charset, there are 2 character slots which appear empty in the application. One is at position 32 (that should be <space>?), the other one is at position 160. When you select any of those two characters and click on <Visualize> or <Save bitmap font as...> in options, the application crashes with a divide by zero error. Selecting any other characters doesn't result in a crash.
Neither corefonts nor native usp10 help. A +relay,+font,+seh,+tid debug log would be probably helpful for those who are good at reading such logs. I can confirm the bug btw.
http://bugs.winehq.org/show_bug.cgi?id=30873
Joachim Durchholz toolforger@durchholz.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |toolforger@durchholz.org
--- Comment #2 from Joachim Durchholz toolforger@durchholz.org 2012-07-18 02:41:44 CDT --- Confirming.
The crash is inside bmfont, not in wine itself. This points towards Wine returning a zero where Windows doesn't.
Here's a workaround: 1) Remove characters 32 and 160 (these are indeed blanks, as GyB suspected). 2) Generate the font normally. 3) Open the .fnt file in a text editor and manually add #32 and #160.
For the manually added characters, here's a model line from a font generated in Windows: char id=32 x=61 y=18 width=1 height=0 xoffset=0 yoffset=11 xadvance=7 page=0 chnl=15
You may have to combine this with what you find in the generated .fnt file, and maybe change the offsets to an unused area in the generated bitmap file. Also, don't forget to increase the character count in the font file...
Disclaimer: Untested.
I have to go now, but I'll return with a trace and a tested workaround as soon as I can (probably this evening).
http://bugs.winehq.org/show_bug.cgi?id=30873
--- Comment #3 from Joachim Durchholz toolforger@durchholz.org 2012-07-18 16:29:28 CDT --- Okay, the workaround is really simple: Add a line for char=32, set x and y to the top-left coordinate of an unused area on the bitmap (i.e. on a 128x128 bitmap, I'd set this to x=120, y=120), set width to 1, height to 0, and use an xadvance value that gives a "reasonable" width for the blank spaces. Repeat for 160 if you need that. Increase "chars count" if the library you're using insists that that value is consistent with the actual number of "char" lines. (For jme3, I know it does not.)
The downside is that you have to guess the width of a space. And you lose any kerning that might be happening with spaces - if there is such a kerning, which I doubt but am not sure. Either way, the width of spaces will probably be off a bit. That's a good-enough workaround until this gets fixed, at least for me.
http://bugs.winehq.org/show_bug.cgi?id=30873
--- Comment #4 from Joachim Durchholz toolforger@durchholz.org 2012-07-18 16:46:30 CDT --- I wanted to attach a debug trace but it turned out to be half a gigabyte, so I refrained from that. I'm willing to try different things as instructed.
https://bugs.winehq.org/show_bug.cgi?id=30873
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |Abandoned?
--- Comment #5 from Ken Sharp imwellcushtymelike@gmail.com --- Is this still an issue in Wine 1.7.45 or later?
https://bugs.winehq.org/show_bug.cgi?id=30873
--- Comment #6 from Joachim Durchholz toolforger@durchholz.org --- BMFont 1.12 is no longer available for download it seems, but 1.13 is still listed as current stable on http://www.angelcode.com/products/bmfont/ so I guess it's still not abandonware. I don't know whether the problem still exists for 1.13; I haven't used BMFont or Wine in years. For those who have Wine installed, it should be straightforward to verify whether the problem still exists or not.
https://bugs.winehq.org/show_bug.cgi?id=30873
Béla Gyebrószki gyebro69@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords|Abandoned? | Status|NEW |RESOLVED Resolution|--- |FIXED
--- Comment #7 from Béla Gyebrószki gyebro69@gmail.com --- The problem is not reproducible with the current stable version of Bmfont, that is v1.13. I still have Bmfont v1.12 on my hdd and the crash is present in 1.6.2 but not in 1.7.45.
Marking fixed.
https://bugs.winehq.org/show_bug.cgi?id=30873
--- Comment #8 from Joachim Durchholz toolforger@durchholz.org --- Sweet. Good to know, and thanks for all the work!
https://bugs.winehq.org/show_bug.cgi?id=30873
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #9 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 1.7.46.
-
wine-bugs＠winehq.org