Re: Major document corruption

2014-06-17 Thread Peter Kümmel 

On 16.06.2014 22:35, Murat Yildizoglu wrote:

Is this bug that haunts the new version is specific to the OSX version?
I am so stressed that I save every two minutes :-(


You mean you copy the file, so lyx can't touch it any more?
Saving by LyX alone doesn't help, because saving with LyX could also destroy 
your files.



Le lundi 16 juin 2014, Maria Gouskova gousk...@gmail.com 
mailto:gousk...@gmail.com a écrit :

Hi all,

So LyX (2.1.0, Mac OS 10.6) stopped responding after I did something
fairly routine to a file (adding references), and I forced the program
to quit. Now I can reopen LyX, but the file I was working on will not
open--LyX just beachballs. To figure this out, I opened the .lyx file
in a text editor, and saw that about 2/3rds of the file just got
lopped off! The lyx.emergency file is missing those parts, too. I
restored the previous version of the file via Dropbox so I didn't lose
much work.

So, is it this?

http://www.lyx.org/trac/ticket/9049

Maria



--


*Prof. Murat Yildizoglu*

Note: Please use the following address as such

UNIVERSITE DE BORDEAUX
GREThA (UMR CNRS 5113)
MURAT YILDIZOGLU
16 AVENUE LEON DUGUIT
CS 50057
33608 PESSAC CEDEX
FRANCE

Bureau : E-331

mail: yildi-at-u-bordeaux4.fr http://yildi-at-u-bordeaux4.fr

web: yildizoglu.info http://yildizoglu.info

Re: Major document corruption

2014-06-17 Thread Peter Kümmel 

On 16.06.2014 22:35, Murat Yildizoglu wrote:

Is this bug that haunts the new version is specific to the OSX version?
I am so stressed that I save every two minutes :-(


On Linux you could setup a cron job which calls a script:

crontab -e

http://stackoverflow.com/questions/5398014/using-crontab-to-execute-script-every-minute-and-another-every-24-hours



Le lundi 16 juin 2014, Maria Gouskova gousk...@gmail.com 
mailto:gousk...@gmail.com a écrit :

Hi all,

So LyX (2.1.0, Mac OS 10.6) stopped responding after I did something
fairly routine to a file (adding references), and I forced the program
to quit. Now I can reopen LyX, but the file I was working on will not
open--LyX just beachballs. To figure this out, I opened the .lyx file
in a text editor, and saw that about 2/3rds of the file just got
lopped off! The lyx.emergency file is missing those parts, too. I
restored the previous version of the file via Dropbox so I didn't lose
much work.

So, is it this?

http://www.lyx.org/trac/ticket/9049

Maria



--


*Prof. Murat Yildizoglu*

Note: Please use the following address as such

UNIVERSITE DE BORDEAUX
GREThA (UMR CNRS 5113)
MURAT YILDIZOGLU
16 AVENUE LEON DUGUIT
CS 50057
33608 PESSAC CEDEX
FRANCE

Bureau : E-331

mail: yildi-at-u-bordeaux4.fr http://yildi-at-u-bordeaux4.fr

web: yildizoglu.info http://yildizoglu.info

Re: Major document corruption

2014-06-17 Thread Maria Gouskova 
On Mon, Jun 16, 2014 at 5:08 PM, Richard Heck rgh...@lyx.org wrote:
 On 06/16/2014 04:29 PM, Maria Gouskova wrote:

 Hi all,

 So LyX (2.1.0, Mac OS 10.6) stopped responding after I did something
 fairly routine to a file (adding references), and I forced the program
 to quit. Now I can reopen LyX, but the file I was working on will not
 open--LyX just beachballs. To figure this out, I opened the .lyx file
 in a text editor, and saw that about 2/3rds of the file just got
 lopped off! The lyx.emergency file is missing those parts, too. I
 restored the previous version of the file via Dropbox so I didn't lose
 much work.

 So, is it this?

 http://www.lyx.org/trac/ticket/9049


 Probably. Did the file end with \begin_inset Tabular?

Yes, indeed.

 OSX didn't generate a crash report, did it?

Yes, it did--here it is:


Process: lyx [54211]
Path:/Applications/LyX.app/Contents/MacOS/lyx
Identifier:  org.lyx.lyx
Version: 2.1.0 (???)
Code Type:   X86-64 (Native)
Parent Process:  launchd [44562]

Date/Time:   2014-06-03 15:56:20.189 -0400
OS Version:  Mac OS X 10.6.8 (10K549)
Report Version:  6

Interval Since Last Report:  52471 sec
Crashes Since Last Report:   1
Per-App Interval Since Last Report:  11732 sec
Per-App Crashes Since Last Report:   1
Anonymous UUID:  5484D3D4-2DF6-4C5C-98AC-51E2434C4DC1

Exception Type:  EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x0001041f7000
Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Application Specific Information:
abort() called

Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
0   libSystem.B.dylib 0x7fff800520b6 __kill + 10
1   libSystem.B.dylib 0x7fff800f29f6 abort + 83
2   org.lyx.lyx   0x0001000eb4ed
lyx::Lexer::Pimpl::~Pimpl() + 14189
3   libSystem.B.dylib 0x7fff800641ba _sigtramp + 26
4   libSystem.B.dylib 0x7fe0087b __memcpy + 219
5   QtCore0x000100f66bf9
QString::realloc(int) + 101
6   QtCore0x000100fd14cf
QFileSystemEntry::isAbsolute() const + 55
7   QtCore0x000100fd5208
QFileSystemEngine::absoluteName(QFileSystemEntry const) + 32
8   QtCore0x000100f9bb87
QFileInfoPrivate::getFileName(QAbstractFileEngine::FileName) const +
743
9   QtCore0x000100f9d778
QFileInfo::absoluteFilePath() const + 60
10  org.lyx.lyx   0x0001004c6ae0 void
std::vectorstd::string, std::allocatorstd::string
::_M_initialize_dispatchboost::token_iteratorboost::char_separatorchar,
std::char_traitschar , __gnu_cxx::__normal_iteratorchar const*,
std::string, std::string
(boost::token_iteratorboost::char_separatorchar,
std::char_traitschar , __gnu_cxx::__normal_iteratorchar const*,
std::string, std::string,
boost::token_iteratorboost::char_separatorchar,
std::char_traitschar , __gnu_cxx::__normal_iteratorchar const*,
std::string, std::string, std::__false_type) + 11212
11  org.lyx.lyx   0x0001004b1a64
boost::signal0void, boost::last_valuevoid, int, std::lessint,
boost::functionvoid ()() ::connect(boost::slotboost::functionvoid
()()  const, boost::signals::connect_position) + 464
12  org.lyx.lyx   0x0001004d1a0e
boost::function2void, int, int::operator()(int, int) const + 48
13  org.lyx.lyx   0x0001004d1a67
boost::signals::detail::slot_call_iteratorboost::signals::detail::call_bound2void::callerint,
int, boost::functionvoid ()(int, int) ,
boost::signals::detail::named_slot_map_iterator::dereference() const
+ 47
14  org.lyx.lyx   0x0001004d1a99 void
boost::last_valuevoid::operator()boost::signals::detail::slot_call_iteratorboost::signals::detail::call_bound2void::callerint,
int, boost::functionvoid ()(int, int) ,
boost::signals::detail::named_slot_map_iterator
(boost::signals::detail::slot_call_iteratorboost::signals::detail::call_bound2void::callerint,
int, boost::functionvoid ()(int, int) ,
boost::signals::detail::named_slot_map_iterator,
boost::signals::detail::slot_call_iteratorboost::signals::detail::call_bound2void::callerint,
int, boost::functionvoid ()(int, int) ,
boost::signals::detail::named_slot_map_iterator) const + 23
15  org.lyx.lyx   0x0001004d1ba7
boost::signal2void, int, int, boost::last_valuevoid, int,
std::lessint, boost::functionvoid ()(int, int) ::operator()(int,
int) + 241
16  org.lyx.lyx   0x0001004cff7f
boost::match_results__gnu_cxx::__normal_iteratorchar const*,
std::string, std::allocatorboost::sub_match__gnu_cxx::__normal_iteratorchar
const*, std::string   ::raise_logic_error() + 2987
17  org.lyx.lyx   0x0001002e9f0b
std::tr1::_Function_base::_Base_managerstd::tr1::_Bindint

Re: Major document corruption

2014-06-17 Thread Peter Kümmel 

On 16.06.2014 22:35, Murat Yildizoglu wrote:

Is this bug that haunts the new version is specific to the OSX version?
I am so stressed that I save every two minutes :-(


You mean you copy the file, so lyx can't touch it any more?
Saving by LyX alone doesn't help, because saving with LyX could also destroy 
your files.



Le lundi 16 juin 2014, Maria Gouskova > a écrit :

Hi all,

So LyX (2.1.0, Mac OS 10.6) stopped responding after I did something
fairly routine to a file (adding references), and I forced the program
to quit. Now I can reopen LyX, but the file I was working on will not
open--LyX just beachballs. To figure this out, I opened the .lyx file
in a text editor, and saw that about 2/3rds of the file just got
lopped off! The lyx.emergency file is missing those parts, too. I
restored the previous version of the file via Dropbox so I didn't lose
much work.

So, is it this?

http://www.lyx.org/trac/ticket/9049

Maria



--


*Prof. Murat Yildizoglu*

Note: Please use the following address as such

UNIVERSITE DE BORDEAUX
GREThA (UMR CNRS 5113)
MURAT YILDIZOGLU
16 AVENUE LEON DUGUIT
CS 50057
33608 PESSAC CEDEX
FRANCE

Bureau : E-331

mail: yildi-at-u-bordeaux4.fr 

web: yildizoglu.info

Re: Major document corruption

2014-06-17 Thread Peter Kümmel 

On 16.06.2014 22:35, Murat Yildizoglu wrote:

Is this bug that haunts the new version is specific to the OSX version?
I am so stressed that I save every two minutes :-(


On Linux you could setup a cron job which calls a script:

crontab -e

http://stackoverflow.com/questions/5398014/using-crontab-to-execute-script-every-minute-and-another-every-24-hours



Le lundi 16 juin 2014, Maria Gouskova > a écrit :

Hi all,

So LyX (2.1.0, Mac OS 10.6) stopped responding after I did something
fairly routine to a file (adding references), and I forced the program
to quit. Now I can reopen LyX, but the file I was working on will not
open--LyX just beachballs. To figure this out, I opened the .lyx file
in a text editor, and saw that about 2/3rds of the file just got
lopped off! The lyx.emergency file is missing those parts, too. I
restored the previous version of the file via Dropbox so I didn't lose
much work.

So, is it this?

http://www.lyx.org/trac/ticket/9049

Maria



--


*Prof. Murat Yildizoglu*

Note: Please use the following address as such

UNIVERSITE DE BORDEAUX
GREThA (UMR CNRS 5113)
MURAT YILDIZOGLU
16 AVENUE LEON DUGUIT
CS 50057
33608 PESSAC CEDEX
FRANCE

Bureau : E-331

mail: yildi-at-u-bordeaux4.fr 

web: yildizoglu.info

Re: Major document corruption

2014-06-17 Thread Maria Gouskova 
On Mon, Jun 16, 2014 at 5:08 PM, Richard Heck  wrote:
> On 06/16/2014 04:29 PM, Maria Gouskova wrote:
>>
>> Hi all,
>>
>> So LyX (2.1.0, Mac OS 10.6) stopped responding after I did something
>> fairly routine to a file (adding references), and I forced the program
>> to quit. Now I can reopen LyX, but the file I was working on will not
>> open--LyX just beachballs. To figure this out, I opened the .lyx file
>> in a text editor, and saw that about 2/3rds of the file just got
>> lopped off! The lyx.emergency file is missing those parts, too. I
>> restored the previous version of the file via Dropbox so I didn't lose
>> much work.
>>
>> So, is it this?
>>
>> http://www.lyx.org/trac/ticket/9049
>
>
> Probably. Did the file end with \begin_inset Tabular?

Yes, indeed.

> OSX didn't generate a crash report, did it?

Yes, it did--here it is:


Process: lyx [54211]
Path:/Applications/LyX.app/Contents/MacOS/lyx
Identifier:  org.lyx.lyx
Version: 2.1.0 (???)
Code Type:   X86-64 (Native)
Parent Process:  launchd [44562]

Date/Time:   2014-06-03 15:56:20.189 -0400
OS Version:  Mac OS X 10.6.8 (10K549)
Report Version:  6

Interval Since Last Report:  52471 sec
Crashes Since Last Report:   1
Per-App Interval Since Last Report:  11732 sec
Per-App Crashes Since Last Report:   1
Anonymous UUID:  5484D3D4-2DF6-4C5C-98AC-51E2434C4DC1

Exception Type:  EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x0001041f7000
Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Application Specific Information:
abort() called

Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
0   libSystem.B.dylib 0x7fff800520b6 __kill + 10
1   libSystem.B.dylib 0x7fff800f29f6 abort + 83
2   org.lyx.lyx   0x0001000eb4ed
lyx::Lexer::Pimpl::~Pimpl() + 14189
3   libSystem.B.dylib 0x7fff800641ba _sigtramp + 26
4   libSystem.B.dylib 0x7fe0087b __memcpy + 219
5   QtCore0x000100f66bf9
QString::realloc(int) + 101
6   QtCore0x000100fd14cf
QFileSystemEntry::isAbsolute() const + 55
7   QtCore0x000100fd5208
QFileSystemEngine::absoluteName(QFileSystemEntry const&) + 32
8   QtCore0x000100f9bb87
QFileInfoPrivate::getFileName(QAbstractFileEngine::FileName) const +
743
9   QtCore0x000100f9d778
QFileInfo::absoluteFilePath() const + 60
10  org.lyx.lyx   0x0001004c6ae0 void
std::vector::_M_initialize_dispatch, __gnu_cxx::__normal_iterator, std::string>
>(boost::token_iterator, __gnu_cxx::__normal_iterator, std::string>,
boost::token_iterator, __gnu_cxx::__normal_iterator, std::string>, std::__false_type) + 11212
11  org.lyx.lyx   0x0001004b1a64
boost::signal0::connect(boost::slot const&, boost::signals::connect_position) + 464
12  org.lyx.lyx   0x0001004d1a0e
boost::function2::operator()(int, int) const + 48
13  org.lyx.lyx   0x0001004d1a67
boost::signals::detail::slot_call_iterator,
boost::signals::detail::named_slot_map_iterator>::dereference() const
+ 47
14  org.lyx.lyx   0x0001004d1a99 void
boost::last_value::operator(),
boost::signals::detail::named_slot_map_iterator>
>(boost::signals::detail::slot_call_iterator,
boost::signals::detail::named_slot_map_iterator>,
boost::signals::detail::slot_call_iterator,
boost::signals::detail::named_slot_map_iterator>) const + 23
15  org.lyx.lyx   0x0001004d1ba7
boost::signal2::operator()(int,
int) + 241
16  org.lyx.lyx   0x0001004cff7f
boost::match_results<__gnu_cxx::__normal_iterator, std::allocator > >::raise_logic_error() + 2987
17  org.lyx.lyx   0x0001002e9f0b
std::tr1::_Function_base::_Base_manager const>,
std::tr1::reference_wrapper const>,
std::tr1::reference_wrapper, std::tr1::reference_wrapper,

Re: Major document corruption

2014-06-16 Thread Murat Yildizoglu 
Is this bug that haunts the new version is specific to the OSX version?
I am so stressed that I save every two minutes :-(

Le lundi 16 juin 2014, Maria Gouskova gousk...@gmail.com a écrit :

 Hi all,

 So LyX (2.1.0, Mac OS 10.6) stopped responding after I did something
 fairly routine to a file (adding references), and I forced the program
 to quit. Now I can reopen LyX, but the file I was working on will not
 open--LyX just beachballs. To figure this out, I opened the .lyx file
 in a text editor, and saw that about 2/3rds of the file just got
 lopped off! The lyx.emergency file is missing those parts, too. I
 restored the previous version of the file via Dropbox so I didn't lose
 much work.

 So, is it this?

 http://www.lyx.org/trac/ticket/9049

 Maria



-- 


*Prof. Murat Yildizoglu*

Note: Please use the following address as such

UNIVERSITE DE BORDEAUX
GREThA (UMR CNRS 5113)
MURAT YILDIZOGLU
16 AVENUE LEON DUGUIT
CS 50057
33608 PESSAC CEDEX
FRANCE

Bureau : E-331

mail: yildi-at-u-bordeaux4.fr

web: yildizoglu.info

Re: Major document corruption

2014-06-16 Thread Jürgen Spitzmüller 
2014-06-16 22:35 GMT+02:00 Murat Yildizoglu:

 Is this bug that haunts the new version is specific to the OSX version?
 I am so stressed that I save every two minutes :-(


No, it occurs on all OSes.

Jürgen

Re: Major document corruption

2014-06-16 Thread Richard Heck 

On 06/16/2014 04:29 PM, Maria Gouskova wrote:

Hi all,

So LyX (2.1.0, Mac OS 10.6) stopped responding after I did something
fairly routine to a file (adding references), and I forced the program
to quit. Now I can reopen LyX, but the file I was working on will not
open--LyX just beachballs. To figure this out, I opened the .lyx file
in a text editor, and saw that about 2/3rds of the file just got
lopped off! The lyx.emergency file is missing those parts, too. I
restored the previous version of the file via Dropbox so I didn't lose
much work.

So, is it this?

http://www.lyx.org/trac/ticket/9049


Probably. Did the file end with \begin_inset Tabular?

OSX didn't generate a crash report, did it? We have been having trouble 
getting information
about the cause of this crash. I have been calling it the mystery 
crash. People see it, but

no-one can reproduce it.

LyX 2.1.1 will change the way the file gets saved, so that the original 
file is not over-written
until the new one has successfully been saved. That will at least 
prevent any dataloss except
whatever you've done since the previous save. It should be out within a 
couple weeks.


Richard

Re: Major document corruption

2014-06-16 Thread Murat Yildizoglu 
Is this bug that haunts the new version is specific to the OSX version?
I am so stressed that I save every two minutes :-(

Le lundi 16 juin 2014, Maria Gouskova  a écrit :

> Hi all,
>
> So LyX (2.1.0, Mac OS 10.6) stopped responding after I did something
> fairly routine to a file (adding references), and I forced the program
> to quit. Now I can reopen LyX, but the file I was working on will not
> open--LyX just beachballs. To figure this out, I opened the .lyx file
> in a text editor, and saw that about 2/3rds of the file just got
> lopped off! The lyx.emergency file is missing those parts, too. I
> restored the previous version of the file via Dropbox so I didn't lose
> much work.
>
> So, is it this?
>
> http://www.lyx.org/trac/ticket/9049
>
> Maria
>


-- 


*Prof. Murat Yildizoglu*

Note: Please use the following address as such

UNIVERSITE DE BORDEAUX
GREThA (UMR CNRS 5113)
MURAT YILDIZOGLU
16 AVENUE LEON DUGUIT
CS 50057
33608 PESSAC CEDEX
FRANCE

Bureau : E-331

mail: yildi-at-u-bordeaux4.fr

web: yildizoglu.info

Re: Major document corruption

2014-06-16 Thread Jürgen Spitzmüller 
2014-06-16 22:35 GMT+02:00 Murat Yildizoglu:

> Is this bug that haunts the new version is specific to the OSX version?
> I am so stressed that I save every two minutes :-(
>

No, it occurs on all OSes.

Jürgen

Re: Major document corruption

2014-06-16 Thread Richard Heck 

On 06/16/2014 04:29 PM, Maria Gouskova wrote:

Hi all,

So LyX (2.1.0, Mac OS 10.6) stopped responding after I did something
fairly routine to a file (adding references), and I forced the program
to quit. Now I can reopen LyX, but the file I was working on will not
open--LyX just beachballs. To figure this out, I opened the .lyx file
in a text editor, and saw that about 2/3rds of the file just got
lopped off! The lyx.emergency file is missing those parts, too. I
restored the previous version of the file via Dropbox so I didn't lose
much work.

So, is it this?

http://www.lyx.org/trac/ticket/9049


Probably. Did the file end with \begin_inset Tabular?

OSX didn't generate a crash report, did it? We have been having trouble 
getting information
about the cause of this crash. I have been calling it "the mystery 
crash". People see it, but

no-one can reproduce it.

LyX 2.1.1 will change the way the file gets saved, so that the original 
file is not over-written
until the new one has successfully been saved. That will at least 
prevent any dataloss except
whatever you've done since the previous save. It should be out within a 
couple weeks.


Richard