pd crashed while I was saving a large patch. now, when I open that patch, about a third of the objects are gone, and ALL of the connections. what the heck happened.. and am I totally screwed or can I fix it.
On 06/17/2011 07:37 PM, Cody Loyd wrote:
pd crashed while I was saving a large patch. now, when I open that patch, about a third of the objects are gone, and ALL of the connections. what the heck happened..
In my experience Pd crashes quite often when I save. In some cases, it crashes _before_ it saves the file, so any change I've made since the last save is lost; in some other cases, it crashes just _after_ saving, so the changes are saved.
It never happened to me that after such a crash I got a corrupted patch or that I loose any object that were present the previous time I had saved the patch. I don't know whether it is your case. Maybe the objects that are gone are those that you had added after the last-but-one save and before the save that triggered the crash.
and am I totally screwed or can I fix it.
If that is the case, I'm afraid there's no fix :(
The problem is not that is just didn't save... So dang.
Pd has been crashing more often for me lately, with no more terminal output than "Segmentation fault"... Is there a log somewhere where I can try to see what's causing these?
On Linux.
Sent from my iPad
On Jun 17, 2011, at 4:06 PM, Matteo Sisti Sette matteosistisette@gmail.com wrote:
On 06/17/2011 07:37 PM, Cody Loyd wrote:
pd crashed while I was saving a large patch. now, when I open that patch, about a third of the objects are gone, and ALL of the connections. what the heck happened..
In my experience Pd crashes quite often when I save. In some cases, it crashes _before_ it saves the file, so any change I've made since the last save is lost; in some other cases, it crashes just _after_ saving, so the changes are saved.
It never happened to me that after such a crash I got a corrupted patch or that I loose any object that were present the previous time I had saved the patch. I don't know whether it is your case. Maybe the objects that are gone are those that you had added after the last-but-one save and before the save that triggered the crash.
and am I totally screwed or can I fix it.
If that is the case, I'm afraid there's no fix :(
2011/6/18 Cody Loyd codyloyd@gmail.com
The problem is not that is just didn't save... So dang.
Pd has been crashing more often for me lately, with no more terminal output than "Segmentation fault"... Is there a log somewhere where I can try to see what's causing these?
I also had this problem lately on Linux (when using dsp in some patches), vanilla version 0.43-0, and after going back to 0.42-5 the problem remained. After removing libraries to load one at a time I figured out that not loading zexy anymore solved the problem for me, although that is not the prettiest solution.
Funs
On Linux.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 06/18/2011 06:57 PM, Funs Seelen wrote:
I also had this problem lately on Linux (when using dsp in some patches), vanilla version 0.43-0, and after going back to 0.42-5 the problem remained. After removing libraries to load one at a time I figured out that not loading zexy anymore solved the problem for me, although that is not the prettiest solution.
i would highly appreciate if people would report such bugs [1], rather than mentioning them casually in a sidenote.
zexy has not seen a lot of attention in the last few years (at least not on a fundamental level), so i cannot possibly think of something on th zexy side that would lead to such a catastrophic failure. probably the problem is related to some compilation options.
i'm using zexy quite a lot (though not so much as i used to), and i cannot remember anything like this.
anyhow, the nice way to find out and fix the issue is a proper bug-report, including a description how to trigger the bug (ala "start Pd, load zexy, load no patch, start DSP, crash"), and even better would be to provide a backtrace of the crash.
ghsmdt IOhannes
[1] http://sourceforge.net/tracker/?group_id=55736&atid=478070
2011/6/19 IOhannes m zmölnig zmoelnig@iem.at
i would highly appreciate if people would report such bugs [1], rather than mentioning them casually in a sidenote.
I'm sorry for not following the proper procedure. Although I'm using Pd a lot I wasn't familiar with this bug tracker. Now I am and reported this bug I found out was caused by zexy's [abs~]. Thanks for your advice! Funs
On Jun 19, 2011, at 5:32 PM, Funs Seelen wrote:
2011/6/19 IOhannes m zmölnig zmoelnig@iem.at
i would highly appreciate if people would report such bugs [1], rather than mentioning them casually in a sidenote.
I'm sorry for not following the proper procedure. Although I'm using
Pd a lot I wasn't familiar with this bug tracker. Now I am and
reported this bug I found out was caused by zexy's [abs~]. Thanks
for your advice! Funs
Also in Pd-extended >= 0.40 and Pd vanilla >= 0.43, there is a "report
bug" item on the Help menu which takes you there.
.hc
Looking at things from a more basic level, you can come up with a more
direct solution... It may sound small in theory, but it in practice,
it can change entire economies. - Amy Smith
--- On Sun, 6/19/11, IOhannes m zmölnig zmoelnig@iem.at wrote:
From: IOhannes m zmölnig zmoelnig@iem.at Subject: Re: [PD] pd crashed To: pd-list@iem.at Date: Sunday, June 19, 2011, 9:22 PM -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 06/18/2011 06:57 PM, Funs Seelen wrote:
I also had this problem lately on Linux (when using
dsp in some patches),
vanilla version 0.43-0, and after going back to 0.42-5
the problem remained.
After removing libraries to load one at a time I
figured out that not
loading zexy anymore solved the problem for me,
although that is not the
prettiest solution.
i would highly appreciate if people would report such bugs [1], rather than mentioning them casually in a sidenote.
zexy has not seen a lot of attention in the last few years (at least not on a fundamental level), so i cannot possibly think of something on th zexy side that would lead to such a catastrophic failure. probably the problem is related to some compilation options.
i'm using zexy quite a lot (though not so much as i used to), and i cannot remember anything like this.
anyhow, the nice way to find out and fix the issue is a proper bug-report, including a description how to trigger the bug (ala "start Pd, load zexy, load no patch, start DSP, crash"), and even better would be to provide a backtrace of the crash.
Under the heading "Add Artifact" please add that a backtrace would be useful to include in a bug report[1] (rather than mentioning it casually in a sidenote).
-Jonathan
ghsmdt IOhannes
[1] http://sourceforge.net/tracker/?group_id=55736&atid=478070 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk3+THoACgkQkX2Xpv6ydvRZhACeJXHJbvDF6G32pyt2FAyoZMOX EP8AoMzpfolEbVWyLnNvo/9wEAYxfUEr =F0cQ -----END PGP SIGNATURE-----
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-06-20 03:04, Jonathan Wilkes wrote:
Under the heading "Add Artifact" please add that a backtrace would be useful to include in a bug report[1] (rather than mentioning it casually in a sidenote).
indeed the "Add Artifact" is a bit moody.
nevertheless, i can think of a number of bug reports that do not require a backtrace at all, and it would seem to be even more weird, to ask people to submit a backtrace if they only wanted to point out that the font rendering behaves unseemly and wanted to illustrate that with a simple screenshot.
usually, "more specific info" is requested from the submitter in a second step, which i h ave skipped know as here was already direct communication.
anyhow, it would of cause be great if we could add something more specific than "file" or "artefact", so submitters would know directly what they are expected to submit.
famsdr IOhannes
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
--- On Mon, 6/20/11, IOhannes m zmoelnig zmoelnig@iem.at wrote:
From: IOhannes m zmoelnig zmoelnig@iem.at Subject: Re: [PD] pd crashed To: pd-list@iem.at Date: Monday, June 20, 2011, 9:29 AM -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-06-20 03:04, Jonathan Wilkes wrote:
Under the heading "Add Artifact" please add that a
backtrace
would be useful to include in a bug report[1]
(rather than
mentioning it casually in a sidenote).
indeed the "Add Artifact" is a bit moody.
nevertheless, i can think of a number of bug reports that do not require a backtrace at all, and it would seem to be even more weird, to ask people to submit a backtrace if they only wanted to point out that the font rendering behaves unseemly and wanted to illustrate that with a simple screenshot.
Wow, what a staggeringly complex problem. This is going to require some serious thought... | [del 2] | OMG: "If the bug causes Pd to crash _and_ you know how to do a backtrace, please include the output in the bug report." Or "...please include an attachment with the output."
-Jonathan
usually, "more specific info" is requested from the submitter in a second step, which i h ave skipped know as here was already direct communication.
anyhow, it would of cause be great if we could add something more specific than "file" or "artefact", so submitters would know directly what they are expected to submit.
famsdr IOhannes
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at
mailing list
UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk3+9rsACgkQkX2Xpv6ydvTy2gCghXYKc1N1T2c6rWVY7sZ83OtT TfUAnjvCGF1av7dWO9pg0raP6xDBc7bL =dfQe -----END PGP SIGNATURE-----
-----Inline Attachment Follows-----
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Fri, 17 Jun 2011, Cody Loyd wrote:
pd crashed while I was saving a large patch. now, when I open that patch, about a third of the objects are gone, and ALL of the connections.
The objects are saved before the connections are. If you open a normal pd files, you will see that all #X connect lines are at the end, except for subpatches, each of which is a section starting with #N canvas and ending with #X restore and counting as one subpatch object. The top #N canvas line is different and represents the main patch of the file.
what the heck happened.. and am I totally screwed or can I fix it.
You really, really need a backup of that file.
Any other way to fix it would require a filesystem expert AND a pd expert, and would only work IF your next-to-last saved version is nearly the same as the last version. Those might not be sufficient conditions, and it would be somewhat in the miracle category if it worked (technicians may apply for sainthood status, etcætera).
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
-
Cody Loyd -
Funs Seelen -
Hans-Christoph Steiner -
IOhannes m zmoelnig -
IOhannes m zmölnig
-
Jonathan Wilkes -
Mathieu Bouchard -
Matteo Sisti Sette