Suprisingly, I did not find an enhancement request on the LibreOffice bug tracker with regards to an 64-Bit port of LibreOffice on Windows.
Enhancement request: creating a 64-Bit version also on Windows.
Currently LibreOffice is only as a 64-Bit binary available for Linux, but not for Mac OS X (bug 58663), but not for Windows.
I'll second this! My problem is that there is no Oos version that runs stably on my Windows XP Pro x64 computer. I've found that 3.6 is more stable than 4.0, but I can crash either one by simply using the Format->Page function in Writer. I'm not sure a 64-bit port would fix my problem, but I'd sure like to find out!
I'll third this request!
I too had Libreoffice crash issues, similar to Sam when formatting, but on Windows XP 32-Bit. See bug 60102 and also bug 44595.
Now using LO on Windows 7 64 bit. Would love to have a 64-Bit version for Windows.
Why that be an issue? Office software will never realistically have any problems due to 2GB memory limit.
(In reply to comment #3)
> Why that be an issue? Office software will never realistically have any
> problems due to 2GB memory limit.
Actually, there are spreadsheets and databases that are big enough to benefit from more memory already.
And I can see presentations using large pictures and movies becoming common.
Maybe texts doesn't need so much memory yet, but Microsoft Word 2010 and newer already have 64 bit versions, so why not a 64 bit version for LibreOffice?
It should be the port for win x64 if there already is on linux x64
Adobe ColdFusion has the ability to leverage LibreOffice (or OpenOffice) to convert Word Document files to PDF format. An example of how it gets called is here: http://stackoverflow.com/questions/2292352/is-it-possible-to-convert-a-microsoft-word-document-to-pdf-with-coldfusion This feature works only in the 32 bit version of Adobe ColdFusion because of this bug read further for explanation why.
The 64 bit version of Adobe ColdFusion leverages 64 bit JVM which requires LibreOffice DLLs for the dependencies to be 64 bit as well. Ignoring this and mixing 64 bit Adobe ColdFusion with 32 bit Libreoffice results in the JVM rejecting them with this error, "Can't load IA 32-bit .dll on a AMD 64-bit platform". That pretty much kills the file conversion. The solution is to use a 64 bit version of the dependencies which currently does not exist.
I'm running LibreOffice 18.104.22.168 on 64-bit Windows 7, SP 1.
When I'm editing or formatting really big documents in Writer, LibreOffice often becomes non-responsive ("not responding") for *very* long periods of time. When I have Resource Monitor analyze the wait chain for soffice.bin, it says it's waiting for splwow64.exe, which I gather is 64-bit Windows' printer spooler for printing from 32-bit applications to 64-bit drivers. Then again, when LibreOffice Writer has become responsive again, is doing nothing, and its share of CPU is 0%, Resource Monitor says its *still* waiting for splwow64.exe.
I don't know enough about Windows or LibreOffice to hazard an informed guess, but is it possible that 32-bit LibreOffice's interaction with splwow64.exe is causing my hangs and that this problem would disappear with a 64-bit version of Libreoffice?
Just throwing it out there as a possibility...
The reason for a 64-bit version of the office suite is to allow applications which WOULD benefit from 64-bit capability to leverage LibreOffice functionality. If my engineering application needs to have an embedded spreadsheet it cannot currently use LibreOffice under win64 without writing some sort of horrible COM-based thing.
I am currently working on a Qt app that needs to have embedded spreadsheet functionality. The contract requirements are that it be open source, be 64-bit, and work under both Linux and Windows. A 64-bit version of LibreOffice would be really useful at this time.
@B.Cook: I am not a developer, but maybe this information here is already helpful for you: As far as I understood a 64-Bit version for Windows is generally working with lots of minor problems. Since you do not need the GUI for your project, maybe it is already good enough for you. In a recent blog entry by Michael Meeks some short news on the 64-bit port: https://people.gnome.org/~michael/blog/2014-07-08.html
Thanks, I'll look into that!
It looks like Windows 10 will drop support for Win32 apps. I'm not sure why MS would make such a move but this is cause for concern.
Lol wut? 64-bit applications are Win32 too.
Nope, MS is removing WoW in Windows 10. Only 64bit apps from now on.
There's also another reason to have a natvie 64bits windows build.
Consider a workstation having oracle native client + java 64 bits runtime.
Consider having drivers to connect to postgresql, mysql, ms-sql whatever here as native 64 bits drivers due to the fact that 3rd professional apps need them.
Now for example install autodesk 64bits, you want to have mdb(x) access and thus you HAVE TO use the 64bits office drivers (and eventually applications).
Now MS doesn't allow you to co-install those drivers in 64 and 32 bits.
Guess what, all future planification in enterprise to create a pure only 64bits application, drop LibreOffice just because the product doesn't exist.
Now if we want to see still Loo installed on future computers, we have to offer this build. Time to propose it now, so beta users can try it, and improve.
(In reply to pquiring from comment #13)
> Nope, MS is removing WoW in Windows 10. Only 64bit apps from now on.
I'm pretty sure this is either a misunderstanding or a canard. There's an unconfirmed rumor that Microsoft is considering dropping the native 32-bit version of Windows 10, but I've found no evidence anywhere that they are considering dropping the WoW64 (Windows 32-bit on Windows 64-bit) subsystem from 64-bit Windows 10.
Here are two articles that suggest that Wow will be stripped:
I'm shocked myself. I can see them not created a 32bit system, but dropping WoW seems a little too soon.
After looking at those articles again I'm not sure WoW64 will be dropped. The first article is from 2011.
(In reply to pquiring from comment #16)
> Here are two articles that suggest that Wow will be stripped:
> I'm shocked myself. I can see them not created a 32bit system, but dropping
> WoW seems a little too soon.
The first article is from 2011, and the second says nothing about WoW64 being dropped. As for Mozilla finally preparing an official release of Firefox x64, well, everyone else is doing it and some 32-bit Firefox users have actually run up against its 2GB RAM limit in real life. The Wikipedia article on WoW64 states that WoW64 is included in 64-bit Windows 10, and I just read a post by someone who claims to be running 32-bit Firefox nightlies on 64-bit Windows 10 Preview. Finally, after generating so much ill will by terminating support for Windows XP, terminating sales of Windows 7, and forcing a tablet-centric Windows 8 on traditional desktop users, it seems highly unlikely that Microsoft would be willing to incur even more resentment by ending support for the huge existing base of 32-bit Windows apps. (If you're running 64-bit Windows now, go to your C:\Program Files (x86) folder and see how many 32-bit apps *you're* using. How many do you think will be promptly rewritten in 64-bit free of charge?) So again, my vote is for misunderstanding or canard.
Adding self to CC if not already on
There are no reasons to -not- make LO64. I might be wrong but Google Chrome64 was made cuz it's more secure, so LO64 should be too, if done correctly. And the performance improvement in addition to RAM limit removal (or at least increment).
Restricted version of LibreOffice (with some modules disabled) is up and running on Windows 64 bit. See this announcement on the dev ML. Ongoing efforts are tracked on this Wiki page:
(In reply to DavidO from comment #21)
> Restricted version of LibreOffice (with some modules disabled) is up and
> running on Windows 64 bit. See this announcement on the dev ML. Ongoing
> efforts are tracked on this Wiki page:
>  https://wiki.documentfoundation.org/Development/msvc-x86_64
Wow, so many issues with the x64.
(In reply to DavidO from https://bugs.documentfoundation.org
> @Stuart, thanks for providing the link for the workaround. There is another
> issue tracking the availability of LO build on 64-bit windows . Could you
> please perform a quick smoke test for LibreOffice 64-bit build? Does it
> looks sane to you?
Loaded up the 2015-02-09 build side by side with current 32-bit TB builds, very solid!
I've tested the alpha0 builds and they work great except that file associations do not register. I can create the associations in Windows for now.
(In reply to pquiring from comment #24)
> I've tested the alpha0 builds and they work great except that file
> associations do not register. I can create the associations in Windows for
This is expected, because the build was done without --enable-release switch.
You can force it though, use:
msiexec /i LibreOrrice.msi WRITE_REGISTRY=1
too much support for a busy os...