Files don't open after today's software update!
Forum rules
Be nice to others! Read the FreeCAD code of conduct!
Be nice to others! Read the FreeCAD code of conduct!
Re: Files don't open after today's software update!
Dear Ulrich,
thank you for your efforts!! I can open the file that you transferred to 0.16!
As to the Sketcher: I am still experimenting with FreeCAD and trying different ways of getting to the desired results. Yes, I have tried the Sketcher for other parts and it gave me a hard time... Maybe I should have another close look at it. Thanks for your note!
Best regards
Jon
thank you for your efforts!! I can open the file that you transferred to 0.16!
As to the Sketcher: I am still experimenting with FreeCAD and trying different ways of getting to the desired results. Yes, I have tried the Sketcher for other parts and it gave me a hard time... Maybe I should have another close look at it. Thanks for your note!
Best regards
Jon
Re: Files don't open after today's software update!
Works again - great, big THANKS!
/Chris
/Chris
electrical engineer
Ubuntu or Mint
Mendel 3d-printer/OctoPrint
LinuxCNC
Optimum BF20L mill
Ubuntu or Mint
Mendel 3d-printer/OctoPrint
LinuxCNC
Optimum BF20L mill
Re: Files don't open after today's software update!
@sebimweb Do you still have problems to open your old projects?
Re: Files don't open after today's software update!
I get:wmayer wrote:
Code: Select all
Traceback (most recent call last):
File "<string>", line 1, in <module>
<type 'exceptions.IOError'>: Invalid project file /home/f3nix/devel/LULZBOT/TAZ 5 - FreeCAD/Test 2/TAZ 5 Final Assembly V0.1.fcstd: basic_string::_M_construct null not valid
OS: Debian GNU/Linux 9.0 (stretch)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.17.10124 (Git)
Build type: Debug
Branch: master
Hash: 5cb17a6036ab9091b9bf9ad46bc0632bbc98d806
Python version: 2.7.13
Qt version: 5.7.1
Coin version: 4.0.0a
OCC version: 7.1.0
Cheers,
Mateusz
Re: Files don't open after today's software update!
Hello wmayer!
It's great - after today's update I can open my old files in FreeCAD 0.17 again! Thanks a lot, everything is fine - whatever has been done.
As for 0.16, it still fails, but as others said this is probably a downward compatibility problem. Although I do not think I used any specific 0.17 features, I understand that this may happen and I will be more careful with using 0.17.
Thanks again for the amazing amount of help in the forum.
Best regards
Jon
It's great - after today's update I can open my old files in FreeCAD 0.17 again! Thanks a lot, everything is fine - whatever has been done.
As for 0.16, it still fails, but as others said this is probably a downward compatibility problem. Although I do not think I used any specific 0.17 features, I understand that this may happen and I will be more careful with using 0.17.
Thanks again for the amazing amount of help in the forum.
Best regards
Jon
Re: Files don't open after today's software update!
To me it looks like a new issue.Is it related or a new issue?
To me it looks like a null pointer is assigned to a std::string which is not allowed. But funny that it raises an exception instead of crashing immediately. Do you get this error only with "TAZ 5 Final Assembly V0.1.fcstd" or any other project file?<type 'exceptions.IOError'>: Invalid project file /home/f3nix/devel/LULZBOT/TAZ 5 - FreeCAD/Test 2/TAZ 5 Final Assembly V0.1.fcstd: basic_string::_M_construct null not valid
Re: Files don't open after today's software update!
That's good.sebimweb wrote:It's great - after today's update I can open my old files in FreeCAD 0.17 again! Thanks a lot, everything is fine - whatever has been done.
Of course the 0.16 cannot fully read in files created with 0.17 when there are changes about new object types and so. However, the reading mechanism is implemented quite flexible so that 0.16 should just ignore information it cannot handle but it should never ever crash. So, this needs some more attention...sebimweb wrote:As for 0.16, it still fails, but as others said this is probably a downward compatibility problem. Although I do not think I used any specific 0.17 features, I understand that this may happen and I will be more careful with using 0.17.
Re: Files don't open after today's software update!
Is that a file you made yourself, or downloaded from devel.lulzbot.com? I can't find it on their website.f3nix wrote:Code: Select all
/home/f3nix/devel/LULZBOT/TAZ 5 - FreeCAD/Test 2/TAZ 5 Final Assembly V0.1.fcstd
FYI I made for them the first ever FreeCAD files of the prototype printer that would become the TAZ, at the time it was named TK-0.
Re: Files don't open after today's software update!
Found it here:NormandC wrote:Is that a file you made yourself, or downloaded from devel.lulzbot.com? I can't find it on their website.
https://forum.lulzbot.com/viewtopic.php?t=2605
Loads fine for me.
Ulrich
OS: Debian GNU/Linux 8.7 (jessie)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.17.10151 (Git)
Build type: Release
Branch: Rueck6
Hash: 6f1fce7e76bfe76076e7bf5cd4a3004cafb0f719
Python version: 2.7.9
Qt version: 4.8.6
Coin version: 4.0.0a
OCC version: 7.1.0
Re: Files don't open after today's software update!
Hi.wmayer wrote:To me it looks like a new issue.Is it related or a new issue?
To me it looks like a null pointer is assigned to a std::string which is not allowed. But funny that it raises an exception instead of crashing immediately. Do you get this error only with "TAZ 5 Final Assembly V0.1.fcstd" or any other project file?<type 'exceptions.IOError'>: Invalid project file /home/f3nix/devel/LULZBOT/TAZ 5 - FreeCAD/Test 2/TAZ 5 Final Assembly V0.1.fcstd: basic_string::_M_construct null not valid
I have some more info on this:
1. I have one more file that gives me this problem (downloaded from the forum and reattached here).
2. Qt4 build is not affected.
3. Happens only on clean start.
4. When I first open a "good file" the "bad file" opens as expected. Creating a new document and inserting an object in it seems to work too (instead of opening a "good file").
5. After a bisect I came up with this:
0700345049fc5c7a32bb6568878e3da5b8f43cc0 is the first bad commit
commit 0700345049fc5c7a32bb6568878e3da5b8f43cc0
Author: wmayer <wmayer@users.sourceforge.net>
Date: Sat Feb 11 16:43:58 2017 +0100
make vboAvailable a static variable and extend interface of renderShape to avoid side effects
But I do not see anything obvious in this changeset.
The exception seems to come from Document.cpp line 2191.
Code: Select all
signalNewObject(*pcObject);
I have seen it before and was amazed that you could pull it off then!NormandC wrote: FYI I made for them the first ever FreeCAD files of the prototype printer that would become the TAZ, at the time it was named TK-0.
Cheers,
Mateusz
- Attachments
-
- FC_jumping_walls.fcstd
- (17.24 KiB) Downloaded 33 times